Offset of International Mobile Subscriber Identity

ABSTRACT

A wireless device derives first paging occasions of a first public land mobile network (PLMN) based on an international mobile subscriber identity (IMSI) of the wireless device and second paging occasions of a second PLMN. The wireless device determines a collision between the first paging occasions and the second paging occasions. Based on determining the collision, the wireless device sends, to a core network node of the first PLMN, a requested IMSI offset value for offsetting the IMSI of the wireless device. the wireless device receives, from the core network node, an accepted IMSI offset value for offsetting the IMSI of the wireless device. The wireless device monitors third paging occasions of the first PLMN. The third paging occasions are derived based on an alternative IMSI equal to a sum of the IMSI of the wireless device and the accepted IMSI offset value.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/846,005, filed Apr. 10, 2020, which claims the benefit of U.S.Provisional Application No. 62/833,264, filed Apr. 12, 2019, all ofwhich are hereby incorporated by reference in their entirety.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Examples of several of the various embodiments of the present inventionare described herein with reference to the drawings.

FIG. 1 is a diagram of an example 5G system architecture as per anaspect of an embodiment of the present disclosure.

FIG. 2 is a diagram of an example 5G System architecture as per anaspect of an embodiment of the present disclosure.

FIG. 3 is a system diagram of an example wireless device and a networknode in a 5G system as per an aspect of an embodiment of the presentdisclosure.

FIG. 4 is a system diagram of an example wireless device as per anaspect of an embodiment of the present disclosure.

FIG. 5A and FIG. 5B depict two registration management state models inUE 100 and AMF 155 as per an aspect of embodiments of the presentdisclosure.

FIG. 6A and FIG. 6B depict two connection management state models in UE100 and AMF 155 as per an aspect of embodiments of the presentdisclosure.

FIG. 7 is diagram for classification and marking traffic as per anaspect of an embodiment of the present disclosure.

FIG. 8 is an example call flow as per an aspect of an embodiment of thepresent disclosure.

FIG. 9 is an example call flow as per an aspect of an embodiment of thepresent disclosure.

FIG. 10 is an example call flow as per an aspect of an embodiment of thepresent disclosure.

FIG. 11 is an example call flow as per an aspect of an embodiment of thepresent disclosure.

FIG. 12 is an example call flow as per an aspect of an embodiment of thepresent disclosure.

FIG. 13 is an example call flow as per an aspect of an embodiment of thepresent disclosure.

FIG. 14 is an example radio resource control (RRC) state transitionaspect as per an aspect of an embodiment of the present disclosure.

FIG. 15 is an example call flow for RRC state transaction as per anaspect of an embodiment of the present disclosure.

FIG. 16 is an example call flows of paging procedure for a UE in CM-IDLEstate

FIG. 17 is an example call flows of RAN paging procedure for a UE inRRC-INACTIVE state.

FIG. 18 is an example radio frame structure for paging monitoringoccasion.

FIG. 19A is an example parameters value for DRX parameters

FIG. 19B is an example parameter for paging occasion calculation.

FIG. 19C is an example equation to derive paging frame and pagingoccasion for E-UTRA.

FIG. 19D is an example equation to derive paging frame and pagingoccasion for new radio (NR)

FIG. 20A is an example value for subframe patterns for paging occasionfor frequency division duplexing case.

FIG. 20B is an example value for subframe patterns for paging occasionfor time division duplexing case.

FIG. 21A is an example structure of an international mobile subscriberidentities (IMSI).

FIG. 21B is an example structure of 4G UE identifiers.

FIG. 21C is an example structure of 5G UE identifiers.

FIG. 22 is a diagram of an example multi-subscriber identity module(SIM) device architecture.

FIG. 23 is a diagram of an example 5G system architecture for dual-SIMdevice.

FIG. 24 is a diagram of an example 4G and 5G network architecture fordual-SIM device.

FIG. 25 is an example diagram for simultaneously monitoring twodifferent PLMNs by a dual-SIM device.

FIG. 26A illustrates an example embodiment of a present disclosure.

FIG. 26B illustrates an example embodiment of a present disclosure.

FIG. 27A illustrates an example embodiment of a present disclosure usingpaging offset.

FIG. 27B illustrates an example embodiment of a present disclosure usingpaging retransmission.

FIG. 27C illustrates an example embodiment of a present disclosure usingUE specific discontinuous reception (DRX).

FIG. 28 illustrates an example embodiment of a present disclosure forpaging adjustment procedure.

FIG. 29 illustrates an example embodiment of a present disclosure for UEin CM-IDLE state.

FIG. 30 illustrates an example embodiment of a present disclosure for UEin RRC-INACTIVE state.

FIG. 31 illustrates an example embodiment of a paging parametersconfiguration procedure.

FIG. 32 illustrates an example flow chart from a wireless device for thepresent disclosure.

FIG. 33 illustrates an example flow chart from a wireless device for thepresent disclosure.

FIG. 34 illustrates an example flow chart from a wireless device for thepresent disclosure.

FIG. 35 is a flow diagram of an aspect of an example embodiment of thepresent disclosure.

FIG. 36 is a flow diagram of an aspect of an example embodiment of thepresent disclosure.

FIG. 37 is a flow diagram of an aspect of an example embodiment of thepresent disclosure.

DETAILED DESCRIPTION OF EXAMPLES

Example embodiments of the present invention enable implementation ofenhanced features and functionalities in 4G/5G systems. Embodiments ofthe technology disclosed herein may be employed in the technical fieldof 4G/5G systems and network slicing for communication systems. Moreparticularly, the embodiments of the technology disclosed herein mayrelate to 5G core network and 5G systems for network slicing incommunication systems. Throughout the present disclosure, UE, wirelessdevice, and mobile device are used interchangeably.

The following acronyms are used throughout the present disclosure:

5G 5th generation mobile networks

5GC 5G Core Network

5GS 5G System

5G-AN 5G Access Network

5QI 5G QoS Indicator

ACK Acknowledgement

AF Application Function

AMF Access and Mobility Management Function

AN Access Network

CDR Charging Data Record

CCNF Common Control Network Functions

CIoT Cellular IoT

CN Core Network

CP Control Plane

DDN Downlink Data Notification

DL Downlink

DN Data Network

DNN Data Network Name

DRX Discontinuous Reception

F-TEID Fully Qualified TEID

gNB next generation Node B

GPSI Generic Public Subscription Identifier

GTP GPRS Tunneling Protocol

GUTI Globally Unique Temporary Identifier

HPLMN Home Public Land Mobile Network

IMSI International Mobile Subscriber Identity

LADN Local Area Data Network

LI Lawful Intercept

MEI Mobile Equipment Identifier

MICO Mobile Initiated Connection Only

MME Mobility Management Entity

MO Mobile Originated

MSISDN Mobile Subscriber ISDN

MT Mobile Terminating

N3IWF Non-3GPP InterWorking Function

NAI Network Access Identifier

NAS Non-Access Stratum

NB-IoT Narrow Band IoT

NEF Network Exposure Function

NF Network Function

NGAP Next Generation Application Protocol

NR New Radio

NRF Network Repository Function

NSI Network Slice Instance

NSSAI Network Slice Selection Assistance Information

NSSF Network Slice Selection Function

OCS Online Charging System

OFCS Offline Charging System

PCF Policy Control Function

PDU Packet/Protocol Data Unit

PEI Permanent Equipment Identifier

PLMN Public Land Mobile Network

PRACH Physical Random Access CHannel

PLMN Public Land Mobile Network

RAN Radio Access Network

QFI QoS Flow Identity

RM Registration Management

S1-AP S1 Application Protocol

SBA Service Based Architecture

SEA Security Anchor Function

SCM Security Context Management

SI System Information

SIB System Information Block

SMF Session Management Function

SMSF SMS Function

S-NSSAI Single Network Slice Selection Assistance information

SUCI Served User Correlation ID

SUPI Subscriber Permanent Identifier

TEID Tunnel Endpoint Identifier

UE User Equipment

UL Uplink

UL CL Uplink Classifier

UPF User Plane Function

VPLMN Visited Public Land Mobile Network

Example FIG. 1 and FIG. 2 depict a 5G system comprising of accessnetworks and 5G core network. An example 5G access network may comprisean access network connecting to a 5G core network. An access network maycomprise an NG-RAN 105 and/or non-3GPP AN 165. An example 5G corenetwork may connect to one or more 5G access networks 5G-AN and/orNG-RANs. 5G core network may comprise functional elements or networkfunctions as in example FIG. 1 and example FIG. 2 where interfaces maybe employed for communication among the functional elements and/ornetwork elements.

In an example, a network function may be a processing function in anetwork, which may have a functional behavior and/or interfaces. Anetwork function may be implemented either as a network element on adedicated hardware, and/or a network node as depicted in FIG. 3 and FIG.4, or as a software instance running on a dedicated hardware and/orshared hardware, or as a virtualized function instantiated on anappropriate platform.

In an example, access and mobility management function, AMF 155, mayinclude the following functionalities (some of the AMF 155functionalities may be supported in a single instance of an AMF 155):termination of RAN 105 CP interface (N2), termination of NAS (N1), NASciphering and integrity protection, registration management, connectionmanagement, reachability management, mobility management, lawfulintercept (for AMF 155 events and interface to LI system), providetransport for session management, SM messages between UE 100 and SMF160, transparent proxy for routing SM messages, access authentication,access authorization, provide transport for SMS messages between UE 100and SMSF, security anchor function, SEA, interaction with the AUSF 150and the UE 100, receiving the intermediate key established as a resultof the UE 100 authentication process, security context management, SCM,that receives a key from the SEA that it uses to derive access networkspecific keys, and/or the like.

In an example, the AMF 155 may support non-3GPP access networks throughN2 interface with N3IWF 170, NAS signaling with a UE 100 over N3IWF 170,authentication of UEs connected over N3IWF 170, management of mobility,authentication, and separate security context state(s) of a UE 100connected via non-3GPP access 165 or connected via 3GPP access 105 andnon-3GPP access 165 simultaneously, support of a coordinated RM contextvalid over 3GPP access 105 and non 3GPP access 165, support of CMmanagement contexts for the UE 100 for connectivity over non-3GPPaccess, and/or the like.

In an example, an AMF 155 region may comprise one or multiple AMF 155sets. The AMF 155 set may comprise some AMF 155 that serve a given areaand/or network slice(s). In an example, multiple AMF 155 sets may be perAMF 155 region and/or network slice(s). Application identifier may be anidentifier that may be mapped to a specific application trafficdetection rule. Configured NSSAI may be an NSSAI that may be provisionedin a UE 100. DN 115 access identifier (DNAI), for a DNN, may be anidentifier of a user plane access to a DN 115. Initial registration maybe related to a UE 100 registration in RM-DEREGISTERED 500, 520 states.N2AP UE 100 association may be a logical per UE 100 association betweena 5G AN node and an AMF 155. N2AP UE-TNLA-binding may be a bindingbetween a N2AP UE 100 association and a specific transport networklayer, TNL association for a given UE 100.

In an example, session management function, SMF 160, may include one ormore of the following functionalities (one or more of the SMF 160functionalities may be supported in a single instance of a SMF 160):session management (e.g. session establishment, modify and release,including tunnel maintain between UPF 110 and AN 105 node), UE 100 IPaddress allocation & management (including optional authorization),selection and control of UP function(s), configuration of trafficsteering at UPF 110 to route traffic to proper destination, terminationof interfaces towards policy control functions, control part of policyenforcement and QoS. lawful intercept (for SM events and interface to LISystem), termination of SM parts of NAS messages, downlink datanotification, initiation of AN specific SM information, sent via AMF 155over N2 to (R)AN 105, determination of SSC mode of a session, roamingfunctionality, handling local enforcement to apply QoS SLAs (VPLMN),charging data collection and charging interface (VPLMN), lawfulintercept (in VPLMN for SM events and interface to LI System), supportfor interaction with external DN 115 for transport of signaling for PDUsession authorization/authentication by external DN 115, and/or thelike.

In an example, a user plane function, UPF 110, may include one or moreof the following functionalities (some of the UPF 110 functionalitiesmay be supported in a single instance of a UPF 110): anchor point forIntra-/Inter-RAT mobility (when applicable), external PDU session pointof interconnect to DN 115, packet routing & forwarding, packetinspection and user plane part of policy rule enforcement, lawfulintercept (UP collection), traffic usage reporting, uplink classifier tosupport routing traffic flows to a data network, branching point tosupport multi-homed PDU session(s), QoS handling for user plane, uplinktraffic verification (SDF to QoS flow mapping), transport level packetmarking in the uplink and downlink, downlink packet buffering, downlinkdata notification triggering, and/or the like.

In an example, the UE 100 IP address management may include allocationand release of the UE 100 IP address and/or renewal of the allocated IPaddress. The UE 100 may set a requested PDU type during a PDU sessionestablishment procedure based on its IP stack capabilities and/orconfiguration. In an example, the SMF 160 may select PDU type of a PDUsession. In an example, if the SMF 160 receives a request with PDU typeset to IP, the SMF 160 may select PDU type IPv4 or IPv6 based on DNNconfiguration and/or operator policies. In an example, the SMF 160 mayprovide a cause value to the UE 100 to indicate whether the other IPversion is supported on the DNN. In an example, if the SMF 160 receivesa request for PDU type IPv4 or IPv6 and the requested IP version issupported by the DNN the SMF 160 may select the requested PDU type.

In an example embodiment, the 5GC elements and UE 100 may support thefollowing mechanisms: during a PDU session establishment procedure, theSMF 160 may send the IP address to the UE 100 via SM NAS signaling. TheIPv4 address allocation and/or IPv4 parameter configuration via DHCPv4may be employed once PDU session may be established. IPv6 prefixallocation may be supported via IPv6 stateless autoconfiguration, ifIPv6 is supported. In an example, 5GC network elements may support IPv6parameter configuration via stateless DHCPv6.

The 5GC may support the allocation of a static IPv4 address and/or astatic IPv6 prefix based on subscription information in a UDM 140 and/orbased on the configuration on a per-subscriber, per-DNN basis.

User plane function(s) (UPF 110) may handle the user plane path of PDUsessions. A UPF 110 that provides the interface to a data network maysupport functionality of a PDU session anchor.

In an example, a policy control function, PCF 135, may support unifiedpolicy framework to govern network behavior, provide policy rules tocontrol plane function(s) to enforce policy rules, implement a front endto access subscription information relevant for policy decisions in auser data repository (UDR), and/or the like.

A network exposure function, NEF 125, may provide means to securelyexpose the services and capabilities provided by the 3GPP networkfunctions, translate between information exchanged with the AF 145 andinformation exchanged with the internal network functions, receiveinformation from other network functions, and/or the like.

In an example, an network repository function, NRF 130 may supportservice discovery function that may receive NF discovery request from NFinstance, provide information about the discovered NF instances (bediscovered) to the NF instance, and maintain information about availableNF instances and their supported services, and/or the like.

In an example, an NSSF 120 may select a set of network slice instancesserving the UE 100, may determine allowed NSSAI. In an example, the NSSF120 may determine the AMF 155 set to be employed to serve the UE 100,and/or, based on configuration, determine a list of candidate AMF 155(s)155 by querying the NRF 130.

In an example, stored data in a UDR may include at least usersubscription data, including at least subscription identifiers, securitycredentials, access and mobility related subscription data, sessionrelated subscription data, policy data, and/or the like.

In an example, an AUSF 150 may support authentication server function(AUSF 150).

In an example, an application function (AF), AF 145, may interact withthe 3GPP core network to provide services. In an example, based onoperator deployment, application functions may be trusted by theoperator to interact directly with relevant network functions.Application functions not allowed by the operator to access directly thenetwork functions may use an external exposure framework (e.g., via theNEF 125) to interact with relevant network functions.

In an example, control plane interface between the (R)AN 105 and the 5Gcore may support connection of multiple different kinds of AN(s) (e.g.3GPP RAN 105, N3IWF 170 for Un-trusted access 165) to the 5GC via acontrol plane protocol. In an example, an N2 AP protocol may be employedfor both the 3GPP access 105 and non-3GPP access 165. In an example,control plane interface between the (R)AN 105 and the 5G core maysupport decoupling between AMF 155 and other functions such as SMF 160that may need to control the services supported by AN(s) (e.g. controlof the UP resources in the AN 105 for a PDU session).

In an example, the 5GC may provide policy information from the PCF 135to the UE 100. In an example, the policy information may comprise:access network discovery and selection policy, UE 100 route selectionpolicy (URSP), SSC mode selection policy (SSCMSP), network sliceselection policy (NSSP), DNN selection policy, non-seamless offloadpolicy, and/or the like.

In an example, as depicted in example FIG. 5A and FIG. 5B, theregistration management, RM may be employed to register or de-register aUE/user 100 with the network and establish the user context in thenetwork. Connection management may be employed to establish and releasethe signaling connection between the UE 100 and the AMF 155.

In an example, a UE 100 may register with the network to receiveservices that require registration. In an example, the UE 100 may updateits registration with the network periodically in order to remainreachable (periodic registration update), or upon mobility (e.g.,mobility registration update), or to update its capabilities or tore-negotiate protocol parameters.

In an example, an initial registration procedure as depicted in exampleFIG. 8 and FIG. 9 may involve execution of network access controlfunctions (e.g. user authentication and access authorization based onsubscription profiles in UDM 140). Example FIG. 9 is a continuation ofthe initial registration procedure depicted in FIG. 8. As a result ofthe initial registration procedure, the identity of the serving AMF 155may be registered in a UDM 140.

In an example, the registration management, RM procedures may beapplicable over both 3GPP access 105 and non 3GPP access 165.

An example FIG. 5A may depict the RM states of a UE 100 as observed bythe UE 100 and AMF 155. In an example embodiment, two RM states may beemployed in the UE 100 and the AMF 155 that may reflect the registrationstatus of the UE 100 in the selected PLMN: RM-DEREGISTERED 500, andRM-REGISTERED 510. In an example, in the RM DEREGISTERED state 500, theUE 100 may not be registered with the network. The UE 100 context in theAMF 155 may not hold valid location or routing information for the UE100 so the UE 100 may not be reachable by the AMF 155. In an example,the UE 100 context may be stored in the UE 100 and the AMF 155. In anexample, in the RM REGISTERED state 510, the UE 100 may be registeredwith the network. In the RM-REGISTERED 510 state, the UE 100 may receiveservices that may require registration with the network.

In an example embodiment, two RM states may be employed in AMF 155 forthe UE 100 that may reflect the registration status of the UE 100 in theselected PLMN: RM-DEREGISTERED 520, and RM-REGISTERED 530.

As depicted in example FIG. 6A and FIG. 6B, connection management, CM,may comprise establishing and releasing a signaling connection between aUE 100 and an AMF 155 over N1 interface. The signaling connection may beemployed to enable NAS signaling exchange between the UE 100 and thecore network. The signaling connection between the UE 100 and the AMF155 may comprise both the AN signaling connection between the UE 100 andthe (R)AN 105 (e.g. RRC connection over 3GPP access) and the N2connection for the UE 100 between the AN and the AMF 155.

As depicted in example FIG. 6A and FIG. 6B, two CM states may beemployed for the NAS signaling connectivity of the UE 100 with the AMF155, CM-IDLE 600, 620 and CM-CONNECTED 610, 630. A UE 100 in CM-IDLE 600state may be in RM-REGISTERED 510 state and may have no NAS signalingconnection established with the AMF 155 over N1. The UE 100 may performcell selection, cell reselection, PLMN selection, and/or the like. A UE100 in CM-CONNECTED 610 state may have a NAS signaling connection withthe AMF 155 over N1.

In an example embodiment two CM states may be employed for the UE 100 atthe AMF 155, CM-IDLE 620 and CM-CONNECTED 630.

In an example, an RRC inactive state may apply to NG-RAN (e.g. it mayapply to NR and E-UTRA connected to 5G CN). The AMF 155, based onnetwork configuration, may provide assistance information to the NG RAN105, to assist the NG RAN's 105 decision whether the UE 100 may be sentto RRC inactive state. When a UE 100 is CM-CONNECTED 610 with RRCinactive state, the UE 100 may resume the RRC connection due to uplinkdata pending, mobile initiated signaling procedure, as a response to RAN105 paging, to notify the network that it has left the RAN 105notification area, and/or the like.

In an example, a NAS signaling connection management may includeestablishing and releasing a NAS signaling connection. A NAS signalingconnection establishment function may be provided by the UE 100 and theAMF 155 to establish the NAS signaling connection for the UE 100 inCM-IDLE 600 state. The procedure of releasing the NAS signalingconnection may be initiated by the 5G (R)AN 105 node or the AMF 155.

In an example, reachability management of a UE 100 may detect whetherthe UE 100 is reachable and may provide the UE 100 location (e.g. accessnode) to the network to reach the UE 100. Reachability management may bedone by paging the UE 100 and the UE 100 location tracking. The UE 100location tracking may include both UE 100 registration area tracking andUE 100 reachability tracking. The UE 100 and the AMF 155 may negotiateUE 100 reachability characteristics in CM-IDLE 600, 620 state duringregistration and registration update procedures.

In an example, two UE 100 reachability categories may be negotiatedbetween a UE 100 and an AMF 155 for CM-IDLE 600, 620 state. 1) UE 100reachability allowing mobile device terminated data while the UE 100 isCM-IDLE 600 mode. 2) Mobile initiated connection only (MICO) mode. The5GC may support a PDU connectivity service that provides exchange ofPDUs between the UE 100 and a data network identified by a DNN. The PDUconnectivity service may be supported via PDU sessions that areestablished upon request from the UE 100.

In an example, a PDU session may support one or more PDU session types.PDU sessions may be established (e.g. upon UE 100 request), modified(e.g. upon UE 100 and 5GC request) and/or released (e.g. upon UE 100 and5GC request) using NAS SM signaling exchanged over N1 between the UE 100and the SMF 160. Upon request from an application server, the 5GC may beable to trigger a specific application in the UE 100. When receiving thetrigger, the UE 100 may send it to the identified application in the UE100. The identified application in the UE 100 may establish a PDUsession to a specific DNN.

In an example, the 5G QoS model may support a QoS flow based frameworkas depicted in example FIG. 7. The 5G QoS model may support both QoSflows that require a guaranteed flow bit rate and QoS flows that may notrequire a guaranteed flow bit rate. In an example, the 5G QoS model maysupport reflective QoS. The QoS model may comprise flow mapping orpacket marking at the UPF 110 (CN_UP) 110, AN 105 and/or the UE 100. Inan example, packets may arrive from and/or destined to theapplication/service layer 730 of UE 100, UPF 110 (CN_UP) 110, and/or theAF 145.

In an example, the QoS flow may be a granularity of QoS differentiationin a PDU session. A QoS flow ID, QFI, may be employed to identify theQoS flow in the 5G system. In an example, user plane traffic with thesame QFI within a PDU session may receive the same traffic forwardingtreatment. The QFI may be carried in an encapsulation header on N3and/or N9 (e.g. without any changes to the end-to-end packet header). Inan example, the QFI may be applied to PDUs with different types ofpayload. The QFI may be unique within a PDU session.

In an example, the QoS parameters of a QoS flow may be provided to the(R)AN 105 as a QoS profile over N2 at PDU session establishment, QoSflow establishment, or when NG-RAN is used at every time the user planeis activated. In an example, a default QoS rule may be required forevery PDU session. The SMF 160 may allocate the QFI for a QoS flow andmay derive QoS parameters from the information provided by the PCF 135.In an example, the SMF 160 may provide the QFI together with the QoSprofile containing the QoS parameters of a QoS flow to the (R)AN 105.

In an example, 5G QoS flow may be a granularity for QoS forwardingtreatment in the 5G system. Traffic mapped to the same 5G QoS flow mayreceive the same forwarding treatment (e.g. scheduling policy, queuemanagement policy, rate shaping policy, RLC configuration, and/or thelike). In an example, providing different QoS forwarding treatment mayrequire separate 5G QoS flows.

In an example, a 5G QoS indicator may be a scalar that may be employedas a reference to a specific QoS forwarding behavior (e.g. packet lossrate, packet delay budget) to be provided to a 5G QoS flow. In anexample, the 5G QoS indicator may be implemented in the access networkby the 5QI referencing node specific parameters that may control the QoSforwarding treatment (e.g. scheduling weights, admission thresholds,queue management thresholds, link layer protocol configuration, and/orthe like).

In an example, 5GC may support edge computing and may enable operator(s)and 3rd party services to be hosted close to the UE's access point ofattachment. The 5G core network may select a UPF 110 close to the UE 100and may execute the traffic steering from the UPF 110 to the local datanetwork via a N6 interface. In an example, the selection and trafficsteering may be based on the UE's 100 subscription data, UE 100location, the information from application function AF 145, policy,other related traffic rules, and/or the like. In an example, the 5G corenetwork may expose network information and capabilities to an edgecomputing application function. The functionality support for edgecomputing may include local routing where the 5G core network may selecta UPF 110 to route the user traffic to the local data network, trafficsteering where the 5G core network may select the traffic to be routedto the applications in the local data network, session and servicecontinuity to enable UE 100 and application mobility, user planeselection and reselection, e.g. based on input from applicationfunction, network capability exposure where 5G core network andapplication function may provide information to each other via NEF 125,QoS and charging where PCF 135 may provide rules for QoS control andcharging for the traffic routed to the local data network, support oflocal area data network where 5G core network may provide support toconnect to the LADN in a certain area where the applications aredeployed, and/or the like.

An example 5G system may be a 3GPP system comprising of 5G accessnetwork 105, 5G core network and a UE 100, and/or the like. AllowedNSSAI may be an NSSAI provided by a serving PLMN during e.g. aregistration procedure, indicating the NSSAI allowed by the network forthe UE 100 in the serving PLMN for the current registration area.

In an example, a PDU connectivity service may provide exchange of PDUsbetween a UE 100 and a data network. A PDU session may be an associationbetween the UE 100 and the data network, DN 115, that may provide thePDU connectivity service. The type of association may be IP, Ethernetand/or unstructured.

Establishment of user plane connectivity to a data network via networkslice instance(s) may comprise the following: performing a RM procedureto select an AMF 155 that supports the required network slices, andestablishing one or more PDU session(s) to the required data network viathe network slice instance(s).

In an example, the set of network slices for a UE 100 may be changed atany time while the UE 100 may be registered with the network, and may beinitiated by the network, or the UE 100.

In an example, a periodic registration update may be UE 100re-registration at expiry of a periodic registration timer. A requestedNSSAI may be a NSSAI that the UE 100 may provide to the network.

In an example, a service based interface may represent how a set ofservices may be provided/exposed by a given NF.

In an example, a service continuity may be an uninterrupted userexperience of a service, including the cases where the IP address and/oranchoring point may change. In an example, a session continuity mayrefer to continuity of a PDU session. For PDU session of IP type sessioncontinuity may imply that the IP address is preserved for the lifetimeof the PDU session. An uplink classifier may be a UPF 110 functionalitythat aims at diverting uplink traffic, based on filter rules provided bythe SMF 160, towards data network, DN 115.

In an example, the 5G system architecture may support data connectivityand services enabling deployments to use techniques such as e.g. networkfunction virtualization and/or software defined networking. The 5Gsystem architecture may leverage service-based interactions betweencontrol plane (CP) network functions where identified. In 5G systemarchitecture, separation of the user plane (UP) functions from thecontrol plane functions may be considered. A 5G system may enable anetwork function to interact with other NF(s) directly if required.

In an example, the 5G system may reduce dependencies between the accessnetwork (AN) and the core network (CN). The architecture may comprise aconverged access-agnostic core network with a common AN-CN interfacewhich may integrate different 3GPP and non-3GPP access types.

In an example, the 5G system may support a unified authenticationframework, stateless NFs, where the compute resource is decoupled fromthe storage resource, capability exposure, and concurrent access tolocal and centralized services. To support low latency services andaccess to local data networks, UP functions may be deployed close to theaccess network.

In an example, the 5G system may support roaming with home routedtraffic and/or local breakout traffic in the visited PLMN. An example 5Garchitecture may be service-based and the interaction between networkfunctions may be represented in two ways. (1) As service-basedrepresentation (depicted in example FIG. 1), where network functionswithin the control plane, may enable other authorized network functionsto access their services. This representation may also includepoint-to-point reference points where necessary. (2) Reference pointrepresentation, showing the interaction between the NF services in thenetwork functions described by point-to-point reference point (e.g. N11)between any two network functions.

In an example, a network slice may comprise the core network controlplane and user plane network functions, the 5G Radio Access Network; theN3IWF functions to the non-3GPP Access Network, and/or the like. Networkslices may differ for supported features and network functionimplementation. The operator may deploy multiple network slice instancesdelivering the same features but for different groups of UEs, e.g. asthey deliver a different committed service and/or because they may bededicated to a customer. The NSSF 120 may store the mapping informationbetween slice instance ID and NF ID (or NF address).

In an example, a UE 100 may simultaneously be served by one or morenetwork slice instances via a 5G-AN. In an example, the UE 100 may beserved by k network slices (e.g. k=8, 16, etc.) at a time. An AMF 155instance serving the UE 100 logically may belong to a network sliceinstance serving the UE 100.

In an example, a PDU session may belong to one specific network sliceinstance per PLMN. In an example, different network slice instances maynot share a PDU session. Different slices may have slice-specific PDUsessions using the same DNN.

An S-NSSAI (Single Network Slice Selection Assistance information) mayidentify a network slice. An S-NSSAI may comprise a slice/service type(SST), which may refer to the expected network slice behavior in termsof features and services; and/or a slice differentiator (SD). A slicedifferentiator may be optional information that may complement theslice/service type(s) to allow further differentiation for selecting anetwork slice instance from potentially multiple network slice instancesthat comply with the indicated slice/service type. In an example, thesame network slice instance may be selected employing differentS-NSSAIs. The CN part of a network slice instance(s) serving a UE 100may be selected by CN.

In an example, subscription data may include the S-NSSAI(s) of thenetwork slices that the UE 100 subscribes to. One or more S-NSSAIs maybe marked as default S-NSSAI. In an example, k S-NSSAI may be markeddefault S-NSSAI (e.g. k=8, 16, etc.). In an example, the UE 100 maysubscribe to more than 8 S-NSSAIs.

In an example, a UE 100 may be configured by the HPLMN with a configuredNSSAI per PLMN. Upon successful completion of a UE's registrationprocedure, the UE 100 may obtain from the AMF 155 an Allowed NSSAI forthis PLMN, which may include one or more S-NSSAIs.

In an example, the Allowed NSSAI may take precedence over the configuredNSSAI for a PLMN. The UE 100 may use the S-NSSAIs in the allowed NSSAIcorresponding to a network slice for the subsequent network sliceselection related procedures in the serving PLMN.

In an example, the establishment of user plane connectivity to a datanetwork via a network slice instance(s) may comprise: performing a RMprocedure to select an AMF 155 that may support the required networkslices, establishing one or more PDU sessions to the required datanetwork via the network slice instance(s), and/or the like.

In an example, when a UE 100 registers with a PLMN, if the UE 100 forthe PLMN has a configured NSSAI or an allowed NSSAI, the UE 100 mayprovide to the network in RRC and NAS layer a requested NSSAI comprisingthe S-NSSAI(s) corresponding to the slice(s) to which the UE 100attempts to register, a temporary user ID if one was assigned to the UE,and/or the like. The requested NSSAI may be configured-NSSAI,allowed-NSSAI, and/or the like.

In an example, when a UE 100 registers with a PLMN, if for the PLMN theUE 100 has no configured NSSAI or allowed NSSAI, the RAN 105 may routeNAS signaling from/to the UE 100 to/from a default AMF 155.

In an example, the network, based on local policies, subscriptionchanges and/or UE 100 mobility, may change the set of permitted networkslice(s) to which the UE 100 is registered. In an example, the networkmay perform the change during a registration procedure or trigger anotification towards the UE 100 of the change of the supported networkslices using an RM procedure (which may trigger a registrationprocedure). The network may provide the UE 100 with a new allowed NSSAIand tracking area list.

In an example, during a registration procedure in a PLMN, in case thenetwork decides that the UE 100 should be served by a different AMF 155based on network slice(s) aspects, the AMF 155 that first received theregistration request may redirect the registration request to anotherAMF 155 via the RAN 105 or via direct signaling between the initial AMF155 and the target AMF 155.

In an example, the network operator may provision the UE 100 withnetwork slice selection policy (NSSP). The NSSP may comprise one or moreNSSP rules.

In an example, if a UE 100 has one or more PDU sessions establishedcorresponding to a specific S-NSSAI, the UE 100 may route the user dataof the application in one of the PDU sessions, unless other conditionsin the UE 100 may prohibit the use of the PDU sessions. If theapplication provides a DNN, then the UE 100 may consider the DNN todetermine which PDU session to use. In an example, if the UE 100 doesnot have a PDU session established with the specific S-NSSAI, the UE 100may request a new PDU session corresponding to the S-NSSAI and with theDNN that may be provided by the application. In an example, in order forthe RAN 105 to select a proper resource for supporting network slicingin the RAN 105, the RAN 105 may be aware of the network slices used bythe UE 100.

In an example, an AMF 155 may select an SMF 160 in a network sliceinstance based on S-NSSAI, DNN and/or other information e.g. UE 100subscription and local operator policies, and/or the like, when the UE100 triggers the establishment of a PDU session. The selected SMF 160may establish the PDU session based on S-NSSAI and DNN.

In an example, in order to support network-controlled privacy of sliceinformation for the slices the UE 100 may access, when the UE 100 isaware or configured that privacy considerations may apply to NSSAI, theUE 100 may not include NSSAI in NAS signaling unless the UE 100 has aNAS security context and the UE 100 may not include NSSAI in unprotectedRRC signaling.

In an example, for roaming scenarios, the network slice specific networkfunctions in VPLMN and HPLMN may be selected based on the S-NSSAIprovided by the UE 100 during PDU connection establishment. If astandardized S-NSSAI is used, selection of slice specific NF instancesmay be done by each PLMN based on the provided S-NSSAI. In an example,the VPLMN may map the S-NSSAI of HPLMN to a S-NSSAI of VPLMN based onroaming agreement (e.g., including mapping to a default S-NSSAI ofVPLMN). In an example, the selection of slice specific NF instance inVPLMN may be done based on the S-NSSAI of VPLMN. In an example, theselection of any slice specific NF instance in HPLMN may be based on theS-NSSAI of HPLMN.

As depicted in example FIG. 8 and FIG. 9, a registration procedure maybe performed by the UE 100 to get authorized to receive services, toenable mobility tracking, to enable reachability, and/or the like.

In an example, the UE 100 may send to the (R)AN 105 an AN message 805(comprising AN parameters, RM-NAS registration request (registrationtype, SUCI or SUPI or 5G-GUTI, last visited TAI (if available), securityparameters, requested NSSAI, mapping of requested NSSAI, UE 100 5GCcapability, PDU session status, PDU session(s) to be re-activated,Follow on request, MICO mode preference, and/or the like), and/or thelike). In an example, in case of NG-RAN, the AN parameters may includee.g. SUCI or SUPI or the 5G-GUTI, the Selected PLMN ID and requestedNSSAI, and/or the like. In an example, the AN parameters may compriseestablishment cause. The establishment cause may provide the reason forrequesting the establishment of an RRC connection. In an example, theregistration type may indicate if the UE 100 wants to perform an initialregistration (e.g. the UE 100 is in RM-DEREGISTERED state), a mobilityregistration update (e.g., the UE 100 is in RM-REGISTERED state andinitiates a registration procedure due to mobility), a periodicregistration update (e.g., the UE 100 is in RM-REGISTERED state and mayinitiate a registration procedure due to the periodic registrationupdate timer expiry) or an emergency registration (e.g., the UE 100 isin limited service state). In an example, if the UE 100 performing aninitial registration (e.g., the UE 100 is in RM-DEREGISTERED state) to aPLMN for which the UE 100 does not already have a 5G-GUTI, the UE 100may include its SUCI or SUPI in the registration request. The SUCI maybe included if the home network has provisioned the public key toprotect SUPI in the UE. If the UE 100 received a UE 100 configurationupdate command indicating that the UE 100 needs to re-register and the5G-GUTI is invalid, the UE 100 may perform an initial registration andmay include the SUPI in the registration request message. For anemergency registration, the SUPI may be included if the UE 100 does nothave a valid 5G-GUTI available; the PEI may be included when the UE 100has no SUPI and no valid 5G-GUTI. In other cases, the 5G-GUTI may beincluded and it may indicate the last serving AMF 155. If the UE 100 isalready registered via a non-3GPP access in a PLMN different from thenew PLMN (e.g., not the registered PLMN or an equivalent PLMN of theregistered PLMN) of the 3GPP access, the UE 100 may not provide over the3GPP access the 5G-GUTI allocated by the AMF 155 during the registrationprocedure over the non-3GPP access. If the UE 100 is already registeredvia a 3GPP access in a PLMN (e.g., the registered PLMN), different fromthe new PLMN (e.g. not the registered PLMN or an equivalent PLMN of theregistered PLMN) of the non-3GPP access, the UE 100 may not provide overthe non-3GPP access the 5G-GUTI allocated by the AMF 155 during theregistration procedure over the 3GPP access. The UE 100 may provide theUE's usage setting based on its configuration. In case of initialregistration or mobility registration update, the UE 100 may include themapping of requested NSSAI, which may be the mapping of each S-NSSAI ofthe requested NSSAI to the S-NSSAIs of the configured NSSAI for theHPLMN, to ensure that the network is able to verify whether theS-NSSAI(s) in the requested NSSAI are permitted based on the subscribedS-NSSAIs. If available, the last visited TAI may be included in order tohelp the AMF 155 produce registration area for the UE. In an example,the security parameters may be used for authentication and integrityprotection. requested NSSAI may indicate the network slice selectionassistance information. The PDU session status may indicates thepreviously established PDU sessions in the UE. When the UE 100 isconnected to the two AMF 155 belonging to different PLMN via 3GPP accessand non-3GPP access then the PDU session status may indicate theestablished PDU session of the current PLMN in the UE. The PDUsession(s) to be re-activated may be included to indicate the PDUsession(s) for which the UE 100 may intend to activate UP connections. APDU session corresponding to a LADN may not be included in the PDUsession(s) to be re-activated when the UE 100 is outside the area ofavailability of the LADN. The follow on request may be included when theUE 100 may have pending uplink signaling and the UE 100 may not includePDU session(s) to be re-activated, or the registration type may indicatethe UE 100 may want to perform an emergency registration.

In an example, if a SUPI is included or the 5G-GUTI does not indicate avalid AMF 155, the (R)AN 105, based on (R)AT and requested NSSAI, ifavailable, may selects 808 an AMF 155. If UE 100 is in CM-CONNECTEDstate, the (R)AN 105 may forward the registration request message to theAMF 155 based on the N2 connection of the UE. If the (R)AN 105 may notselect an appropriate AMF 155, it may forward the registration requestto an AMF 155 which has been configured, in (R)AN 105, to perform AMF155 selection 808.

In an example, the (R)AN 105 may send to the new AMF 155 an N2 message810 (comprising: N2 parameters, RM-NAS registration request(registration type, SUPI or 5G-GUTI, last visited TAI (if available),security parameters, requested NSSAI, mapping of requested NSSAI, UE 1005GC capability, PDU session status, PDU session(s) to be re-activated,follow on request, and MICO mode preference), and/or the like). In anexample, when NG-RAN is used, the N2 parameters may comprise theselected PLMN ID, location information, cell identity and the RAT typerelated to the cell in which the UE 100 is camping. In an example, whenNG-RAN is used, the N2 parameters may include the establishment cause.

In an example, the new AMF 155 may send to the old AMF 155 aNamf_Communication_UEContextTransfer (complete registration request)815. In an example, if the UE's 5G-GUTI was included in the registrationrequest and the serving AMF 155 has changed since last registrationprocedure, the new AMF 155 may invoke theNamf_Communication_UEContextTransfer service operation 815 on the oldAMF 155 including the complete registration request IE, which may beintegrity protected, to request the UE's SUPI and MM Context. The oldAMF 155 may use the integrity protected complete registration request IEto verify if the context transfer service operation invocationcorresponds to the UE 100 requested. In an example, the old AMF 155 maytransfer the event subscriptions information by each NF consumer, forthe UE, to the new AMF 155. In an example, if the UE 100 identifiesitself with PEI, the SUPI request may be skipped.

In an example, the old AMF 155 may send to new AMF 155 a response 815 toNamf_Communication_UEContextTransfer (SUPI, MM context, SMF 160information, PCF ID). In an example, the old AMF 155 may respond to thenew AMF 155 for the Namf_Communication_UEContextTransfer invocation byincluding the UE's SUPI and MM context. In an example, if old AMF 155holds information about established PDU sessions, the old AMF 155 mayinclude SMF 160 information including S-NSSAI(s), SMF 160 identities andPDU session ID. In an example, if old AMF 155 holds information aboutactive NGAP UE-TNLA bindings to N3IWF, the old AMF 155 may includeinformation about the NGAP UE-TNLA bindings.

In an example, if the SUPI is not provided by the UE 100 nor retrievedfrom the old AMF 155 the identity request procedure 820 may be initiatedby the AMF 155 sending an identity request message to the UE 100requesting the SUCI.

In an example, the UE 100 may respond with an identity response message820 including the SUCI. The UE 100 may derive the SUCI by using theprovisioned public key of the HPLMN.

In an example, the AMF 155 may decide to initiate UE 100 authentication825 by invoking an AUSF 150. The AMF 155 may select an AUSF 150 based onSUPI or SUCI. In an example, if the AMF 155 is configured to supportemergency registration for unauthenticated SUPIs and the UE 100indicated registration type emergency registration the AMF 155 may skipthe authentication and security setup or the AMF 155 may accept that theauthentication may fail and may continue the registration procedure.

In an example, the authentication 830 may be performed byNudm_UEAuthenticate_Get operation. The AUSF 150 may discover a UDM 140.In case the AMF 155 provided a SUCI to AUSF 150, the AUSF 150 may returnthe SUPI to AMF 155 after the authentication is successful. In anexample, if network slicing is used, the AMF 155 may decide if theregistration request needs to be rerouted where the initial AMF 155refers to the AMF 155. In an example, the AMF 155 may initiate NASsecurity functions. In an example, upon completion of NAS securityfunction setup, the AMF 155 may initiate NGAP procedure to enable 5G-ANuse it for securing procedures with the UE. In an example, the 5G-AN maystore the security context and may acknowledge to the AMF 155. The 5G-ANmay use the security context to protect the messages exchanged with theUE.

In an example, new AMF 155 may send to the old AMF 155Namf_Communication_RegistrationCompleteNotify 835. If the AMF 155 haschanged, the new AMF 155 may notify the old AMF 155 that theregistration of the UE 100 in the new AMF 155 may be completed byinvoking the Namf_Communication_RegistrationCompleteNotify serviceoperation. If the authentication/security procedure fails, then theregistration may be rejected, and the new AMF 155 may invoke theNamf_Communication_RegistrationCompleteNotify service operation with areject indication reason code towards the old AMF 155. The old AMF 155may continue as if the UE 100 context transfer service operation wasnever received. If one or more of the S-NSSAIs used in the oldregistration area may not be served in the target registration area, thenew AMF 155 may determine which PDU session may not be supported in thenew registration area. The new AMF 155 may invoke theNamf_Communication_RegistrationCompleteNotify service operationincluding the rejected PDU session ID and a reject cause (e.g. theS-NSSAI becomes no longer available) towards the old AMF 155. The newAMF 155 may modify the PDU session status correspondingly. The old AMF155 may inform the corresponding SMF 160(s) to locally release the UE'sSM context by invoking the Nsmf_PDUSession_ReleaseSMContext serviceoperation.

In an example, the new AMF 155 may send to the UE 100 an identityrequest/response 840 (e.g., PEI). If the PEI was not provided by the UE100 nor retrieved from the old AMF 155, the identity request proceduremay be initiated by AMF 155 sending an identity request message to theUE 100 to retrieve the PEI. The PEI may be transferred encrypted unlessthe UE 100 performs emergency registration and may not be authenticated.For an emergency registration, the UE 100 may have included the PEI inthe registration request.

In an example, the new AMF 155 may initiate ME identity check 845 byinvoking the N5g-eir_EquipmentIdentityCheck_Get service operation 845.

In an example, the new AMF 155, based on the SUPI, may select 905 a UDM140. The UDM 140 may select a UDR instance. In an example, the AMF 155may select a UDM 140.

In an example, if the AMF 155 has changed since the last registrationprocedure, or if the UE 100 provides a SUPI which may not refer to avalid context in the AMF 155, or if the UE 100 registers to the same AMF155 it has already registered to a non-3GPP access (e.g., the UE 100 isregistered over a non-3GPP access and may initiate the registrationprocedure to add a 3GPP access), the new AMF 155 may register with theUDM 140 using Nudm_UECM_Registration 910 and may subscribe to benotified when the UDM 140 may deregister the AMF 155. The UDM 140 maystore the AMF 155 identity associated to the access type and may notremove the AMF 155 identity associated to the other access type. The UDM140 may store information provided at registration in UDR, byNudr_UDM_Update. In an example, the AMF 155 may retrieve the access andmobility subscription data and SMF 160 selection subscription data usingNudm_SDM_Get 915. The UDM 140 may retrieve this information from UDR byNudr_UDM_Query(access and mobility subscription data). After asuccessful response is received, the AMF 155 may subscribe to benotified using Nudm_SDM_Subscribe 920 when the data requested may bemodified. The UDM 140 may subscribe to UDR by Nudr_UDM_Subscribe. TheGPSI may be provided to the AMF 155 in the subscription data from theUDM 140 if the GPSI is available in the UE 100 subscription data. In anexample, the new AMF 155 may provide the access type it serves for theUE 100 to the UDM 140 and the access type may be set to 3GPP access. TheUDM 140 may store the associated access type together with the servingAMF 155 in UDR by Nudr_UDM_Update. The new AMF 155 may create an MMcontext for the UE 100 after getting the mobility subscription data fromthe UDM 140. In an example, when the UDM 140 stores the associatedaccess type together with the serving AMF 155, the UDM 140 may initiatea Nudm_UECM_DeregistrationNotification 921 to the old AMF 155corresponding to 3GPP access. The old AMF 155 may remove the MM contextof the UE. If the serving NF removal reason indicated by the UDM 140 isinitial registration, then the old AMF 155 may invoke theNamf_EventExposure_Notify service operation towards all the associatedSMF 160 s of the UE 100 to notify that the UE 100 is deregistered fromold AMF 155. The SMF 160 may release the PDU session(s) on getting thisnotification. In an example, the old AMF 155 may unsubscribe with theUDM 140 for subscription data using Nudm_SDM_unsubscribe 922.

In an example, if the AMF 155 decides to initiate PCF 135 communication,e.g. the AMF 155 has not yet obtained access and mobility policy for theUE 100 or if the access and mobility policy in the AMF 155 are no longervalid, the AMF 155 may select 925 a PCF 135. If the new AMF 155 receivesa PCF ID from the old AMF 155 and successfully contacts the PCF 135identified by the PCF ID, the AMF 155 may select the (V-)PCF identifiedby the PCF ID. If the PCF 135 identified by the PCF ID may not be used(e.g. no response from the PCF 135) or if there is no PCF ID receivedfrom the old AMF 155, the AMF 155 may select 925 a PCF 135.

In an example, the new AMF 155 may perform a policy associationestablishment 930 during registration procedure. If the new AMF 155contacts the PCF 135 identified by the (V-)PCF ID received duringinter-AMF 155 mobility, the new AMF 155 may include the PCF-ID in theNpcf_AMPolicyControl Get operation. If the AMF 155 notifies the mobilityrestrictions (e.g. UE 100 location) to the PCF 135 for adjustment, or ifthe PCF 135 updates the mobility restrictions itself due to someconditions (e.g. application in use, time and date), the PCF 135 mayprovide the updated mobility restrictions to the AMF 155.

In an example, the PCF 135 may invoke Namf_EventExposure_Subscribeservice operation 935 for UE 100 event subscription.

In an example, the AMF 155 may send to the SMF 160 aNsmf_PDUSession_UpdateSMContext 936. In an example, the AMF 155 mayinvoke the Nsmf_PDUSession_UpdateSMContext if the PDU session(s) to bere-activated is included in the registration request. The AMF 155 maysend Nsmf_PDUSession_UpdateSMContext request to SMF 160(s) associatedwith the PDU session(s) to activate user plane connections of the PDUsession(s). The SMF 160 may decide to trigger e.g. the intermediate UPF110 insertion, removal or change of PSA. In the case that theintermediate UPF 110 insertion, removal, or relocation is performed forthe PDU session(s) not included in PDU session(s) to be re-activated,the procedure may be performed without N11 and N2 interactions to updatethe N3 user plane between (R)AN 105 and 5GC. The AMF 155 may invoke theNsmf_PDUSession_ReleaseSMContext service operation towards the SMF 160if any PDU session status indicates that it is released at the UE 100.The AMF 155 may invoke the Nsmf_PDUSession_ReleaseSMContext serviceoperation towards the SMF 160 in order to release any network resourcesrelated to the PDU session.

In an example, the new AMF 155 may send to a N3IWF an N2 AMF 155mobility request 940. If the AMF 155 has changed, the new AMF 155 maycreate an NGAP UE 100 association towards the N3IWF to which the UE 100is connected. In an example, the N3IWF may respond to the new AMF 155with an N2 AMF 155 mobility response 940.

In an example, the new AMF 155 may send to the UE 100 a registrationaccept 955 (comprising: 5G-GUTI, registration area, mobilityrestrictions, PDU session status, allowed NSSAI, [mapping of allowedNSSAI], periodic registration update timer, LADN information andaccepted MICO mode, IMS voice over PS session supported indication,emergency service support indicator, and/or the like). In an example,the AMF 155 may send the registration accept message to the UE 100indicating that the registration request has been accepted. 5G-GUTI maybe included if the AMF 155 allocates a new 5G-GUTI. If the AMF 155allocates a new registration area, it may send the registration area tothe UE 100 via registration accept message 955. If there is noregistration area included in the registration accept message, the UE100 may consider the old registration area as valid. In an example,mobility restrictions may be included in case mobility restrictions mayapply for the UE 100 and registration type may not be emergencyregistration. The AMF 155 may indicate the established PDU sessions tothe UE 100 in the PDU session status. The UE 100 may remove locally anyinternal resources related to PDU sessions that are not marked asestablished in the received PDU session status. In an example, when theUE 100 is connected to the two AMF 155 belonging to different PLMN via3GPP access and non-3GPP access then the UE 100 may remove locally anyinternal resources related to the PDU session of the current PLMN thatare not marked as established in received PDU session status. If the PDUsession status information was in the registration request, the AMF 155may indicate the PDU session status to the UE. The mapping of allowedNSSAI may be the mapping of each S-NSSAI of the allowed NSSAI to theS-NSSAIs of the configured NSSAI for the HPLMN. The AMF 155 may includein the registration accept message 955 the LADN information for LADNsthat are available within the registration area determined by the AMF155 for the UE. If the UE 100 included MICO mode in the request, thenAMF 155 may respond whether MICO mode may be used. The AMF 155 may setthe IMS voice over PS session supported Indication. In an example, inorder to set the IMS voice over PS session supported indication, the AMF155 may perform a UE/RAN radio information and compatibility requestprocedure to check the compatibility of the UE 100 and RAN radiocapabilities related to IMS voice over PS. In an example, the emergencyservice support indicator may inform the UE 100 that emergency servicesare supported, e.g., the UE 100 may request PDU session for emergencyservices. In an example, the handover restriction list and UE-AMBR maybe provided to NG-RAN by the AMF 155.

In an example, the UE 100 may send to the new AMF 155 a registrationcomplete 960 message. In an example, the UE 100 may send theregistration complete message 960 to the AMF 155 to acknowledge that anew 5G-GUTI may be assigned. In an example, when information about thePDU session(s) to be re-activated is not included in the registrationrequest, the AMF 155 may release the signaling connection with the UE100. In an example, when the follow-on request is included in theregistration request, the AMF 155 may not release the signalingconnection after the completion of the registration procedure. In anexample, if the AMF 155 is aware that some signaling is pending in theAMF 155 or between the UE 100 and the 5GC, the AMF 155 may not releasethe signaling connection after the completion of the registrationprocedure.

As depicted in example FIG. 10 and FIG. 11, a service request proceduree.g., a UE 100 triggered service request procedure may be used by a UE100 in CM-IDLE state to request the establishment of a secure connectionto an AMF 155. FIG. 11 is continuation of FIG. 10 depicting the servicerequest procedure. The service request procedure may be used to activatea user plane connection for an established PDU session. The servicerequest procedure may be triggered by the UE 100 or the 5GC, and may beused when the UE 100 is in CM-IDLE and/or in CM-CONNECTED and may allowselectively to activate user plane connections for some of theestablished PDU sessions.

In an example, a UE 100 in CM IDLE state may initiate the servicerequest procedure to send uplink signaling messages, user data, and/orthe like, as a response to a network paging request, and/or the like. Inan example, after receiving the service request message, the AMF 155 mayperform authentication. In an example, after the establishment ofsignaling connection to the AMF 155, the UE 100 or network may sendsignaling messages, e.g. PDU session establishment from the UE 100 to aSMF 160, via the AMF 155.

In an example, for any service request, the AMF 155 may respond with aservice accept message to synchronize PDU session status between the UE100 and network. The AMF 155 may respond with a service reject messageto the UE 100, if the service request may not be accepted by thenetwork. The service reject message may include an indication or causecode requesting the UE 100 to perform a registration update procedure.In an example, for service request due to user data, network may takefurther actions if user plane connection activation may not besuccessful. In an example FIG. 10 and FIG. 11, more than one UPF, e.g.,old UPF 110-2 and PDU session Anchor PSA UPF 110-3 may be involved.

In an example, the UE 100 may send to a (R)AN 105 an AN messagecomprising AN parameters, mobility management, MM NAS service request1005 (e.g., list of PDU sessions to be activated, list of allowed PDUsessions, security parameters, PDU session status, and/or the like),and/or the like. In an example, the UE 100 may provide the list of PDUsessions to be activated when the UE 100 may re-activate the PDUsession(s). The list of allowed PDU sessions may be provided by the UE100 when the service request may be a response of a paging or a NASnotification, and may identify the PDU sessions that may be transferredor associated to the access on which the service request may be sent. Inan example, for the case of NG-RAN, the AN parameters may includeselected PLMN ID, and an establishment cause. The establishment causemay provide the reason for requesting the establishment of an RRCconnection. The UE 100 may send NAS service request message towards theAMF 155 encapsulated in an RRC message to the RAN 105.

In an example, if the service request may be triggered for user data,the UE 100 may identify, using the list of PDU sessions to be activated,the PDU session(s) for which the UP connections are to be activated inthe NAS service request message. If the service request may be triggeredfor signaling, the UE 100 may not identify any PDU session(s). If thisprocedure may be triggered for paging response, and/or the UE 100 mayhave at the same time user data to be transferred, the UE 100 mayidentify the PDU session(s) whose UP connections may be activated in MMNAS service request message, by the list of PDU sessions to beactivated.

In an example, if the service request over 3GPP access may be triggeredin response to a paging indicating non-3GPP access, the NAS servicerequest message may identify in the list of allowed PDU sessions thelist of PDU sessions associated with the non-3GPP access that may bere-activated over 3GPP. In an example, the PDU session status mayindicate the PDU sessions available in the UE 100. In an example, the UE100 may not trigger the service request procedure for a PDU sessioncorresponding to a LADN when the UE 100 may be outside the area ofavailability of the LADN. The UE 100 may not identify such PDUsession(s) in the list of PDU sessions to be activated, if the servicerequest may be triggered for other reasons.

In an example, the (R)AN 105 may send to AMF 155 an N2 Message 1010(e.g., a service request) comprising N2 parameters, MM NAS servicerequest, and/or the like. The AMF 155 may reject the N2 message if itmay not be able to handle the service request. In an example, if NG-RANmay be used, the N2 parameters may include the 5G-GUTI, selected PLMNID, location information, RAT type, establishment cause, and/or thelike. In an example, the 5G-GUTI may be obtained in RRC procedure andthe (R)AN 105 may select the AMF 155 according to the 5G-GUTI. In anexample, the location information and RAT type may relate to the cell inwhich the UE 100 may be camping. In an example, based on the PDU sessionstatus, the AMF 155 may initiate PDU session release procedure in thenetwork for the PDU sessions whose PDU session ID(s) may be indicated bythe UE 100 as not available.

In an example, if the service request was not sent integrity protectedor integrity protection verification failed, the AMF 155 may initiate aNAS authentication/security procedure 1015.

In an example, if the UE 100 triggers the service request to establish asignaling connection, upon successful establishment of the signalingconnection, the UE 100 and the network may exchange NAS signaling.

In an example the AMF 155 may send to the SMF 160 a PDU session updatecontext request 1020 e.g., Nsmf_PDUSession_UpdateSMContext requestcomprising PDU session ID(s), Cause(s), UE 100 location information,access type, and/or the like.

In an example, the Nsmf_PDUSession_UpdateSMContext request may beinvoked by the AMF 155 if the UE 100 may identify PDU session(s) to beactivated in the NAS service request message. In an example, theNsmf_PDUSession_UpdateSMContext request may be triggered by the SMF 160wherein the PDU session(s) identified by the UE 100 may correlate toother PDU session ID(s) than the one triggering the procedure. In anexample, the Nsmf_PDUSession_UpdateSMContext request may be triggered bythe SMF 160 wherein the current UE 100 location may be outside the areaof validity for the N2 information provided by the SMF 160 during anetwork triggered service request procedure. The AMF 155 may not sendthe N2 information provided by the SMF 160 during the network triggeredservice request procedure.

In an example, the AMF 155 may determine the PDU session(s) to beactivated and may send a Nsmf_PDUSession_UpdateSMContext request to SMF160(s) associated with the PDU session(s) with cause set to indicateestablishment of user plane resources for the PDU session(s).

In an example, if the procedure may be triggered in response to pagingindicating non-3GPP access, and the list of allowed PDU sessionsprovided by the UE 100 may not include the PDU session for which the UE100 was paged, the AMF 155 may notify the SMF 160 that the user planefor the PDU session may not be re-activated. The service requestprocedure may succeed without re-activating the user plane of any PDUsessions, and the AMF 155 may notify the UE 100.

In an example, if the PDU session ID may correspond to a LADN and theSMF 160 may determine that the UE 100 may be outside the area ofavailability of the LADN based on the UE 100 location reporting from theAMF 155, the SMF 160 may decide to (based on local policies) keep thePDU session, may reject the activation of user plane connection for thePDU session and may inform the AMF 155. In an example, if the proceduremay be triggered by a network triggered service request, the SMF 160 maynotify the UPF 110 that originated the data notification to discarddownlink data for the PDU sessions and/or to not provide further datanotification messages. The SMF 160 may respond to the AMF 155 with anappropriate reject cause and the user plane activation of PDU sessionmay be stopped.

In an example, if the PDU session ID may correspond to a LADN and theSMF 160 may determine that the UE 100 may be outside the area ofavailability of the LADN based on the UE 100 location reporting from theAMF 155, the SMF 160 may decide to (based on local policies) release thePDU session. The SMF 160 may locally release the PDU session and mayinform the AMF 155 that the PDU session may be released. The SMF 160 mayrespond to the AMF 155 with an appropriate reject cause and the userplane Activation of PDU session may be stopped.

In an example, if the UP activation of the PDU session may be acceptedby the SMF 160, based on the location info received from the AMF 155,the SMF 160 may check the UPF 110 Selection 1025 Criteria (e.g., sliceisolation requirements, slice coexistence requirements, UPF's 110dynamic load, UPF's 110 relative static capacity among UPFs supportingthe same DNN, UPF 110 location available at the SMF 160, UE 100 locationinformation, Capability of the UPF 110 and the functionality requiredfor the particular UE 100 session. In an example, an appropriate UPF 110may be selected by matching the functionality and features required fora UE 100, DNN, PDU session type (e.g. IPv4, IPv6, ethernet type orunstructured type) and if applicable, the static IP address/prefix, SSCmode selected for the PDU session, UE 100 subscription profile in UDM140, DNAI as included in the PCC rules, local operator policies,S-NSSAI, access technology being used by the UE 100, UPF 110 logicaltopology, and/or the like), and may determine to perform one or more ofthe following: continue using the current UPF(s); may select a newintermediate UPF 110 (or add/remove an intermediate UPF 110), if the UE100 has moved out of the service area of the UPF 110 that was previouslyconnecting to the (R)AN 105, while maintaining the UPF(s) acting as PDUsession anchor; may trigger re-establishment of the PDU session toperform relocation/reallocation of the UPF 110 acting as PDU sessionanchor, e.g. the UE 100 has moved out of the service area of the anchorUPF 110 which is connecting to RAN 105.

In an example, the SMF 160 may send to the UPF 110 (e.g., newintermediate UPF 110) an N4 session establishment request 1030. In anexample, if the SMF 160 may select a new UPF 110 to act as intermediateUPF 110-2 for the PDU session, or if the SMF 160 may select to insert anintermediate UPF 110 for a PDU session which may not have anintermediate UPF 110-2, an N4 session establishment request 1030 messagemay be sent to the new UPF 110, providing packet detection, dataforwarding, enforcement and reporting rules to be installed on the newintermediate UPF. The PDU session anchor addressing information (on N9)for this PDU session may be provided to the intermediate UPF 110-2.

In an example, if a new UPF 110 is selected by the SMF 160 to replacethe old (intermediate) UPF 110-2, the SMF 160 may include a dataforwarding indication. The data forwarding indication may indicate tothe UPF 110 that a second tunnel endpoint may be reserved for bufferedDL data from the old I-UPF.

In an example, the new UPF 110 (intermediate) may send to SMF 160 an N4session establishment response message 1030. In case the UPF 110 mayallocate CN tunnel info, the UPF 110 may provide DL CN tunnel info forthe UPF 110 acting as PDU session anchor and UL CN tunnel info (e.g., CNN3 tunnel info) to the SMF 160. If the data forwarding indication may bereceived, the new (intermediate) UPF 110 acting as N3 terminating pointmay send DL CN tunnel info for the old (intermediate) UPF 110-2 to theSMF 160. The SMF 160 may start a timer, to release the resource in theold intermediate UPF 110-2.

In an example, if the SMF 160 may selects a new intermediate UPF 110 forthe PDU session or may remove the old I-UPF 110-2, the SMF 160 may sendN4 session modification request message 1035 to PDU session anchor, PSAUPF 110-3, providing the data forwarding indication and DL tunnelinformation from new intermediate UPF 110.

In an example, if the new intermediate UPF 110 may be added for the PDUsession, the (PSA) UPF 110-3 may begin to send the DL data to the newI-UPF 110 as indicated in the DL tunnel information.

In an example, if the service request may be triggered by the network,and the SMF 160 may remove the old I-UPF 110-2 and may not replace theold I-UPF 110-2 with the new I-UPF 110, the SMF 160 may include the dataforwarding indication in the request. The data forwarding indication mayindicate to the (PSA) UPF 110-3 that a second tunnel endpoint may bereserved for buffered DL data from the old I-UPF 110-2. In this case,the PSA UPF 110-3 may begin to buffer the DL data it may receive at thesame time from the N6 interface.

In an example, the PSA UPF 110-3 (PSA) may send to the SMF 160 an N4session modification response 1035. In an example, if the dataforwarding indication may be received, the PSA UPF 110-3 may become asN3 terminating point and may send CN DL tunnel info for the old(intermediate) UPF 110-2 to the SMF 160. The SMF 160 may start a timer,to release the resource in old intermediate UPF 110-2 if there is one.

In an example, the SMF 160 may send to the old UPF 110-2 an N4 sessionmodification request 1045 (e.g., may comprise new UPF 110 address, newUPF 110 DL tunnel ID, and/or the like). In an example, if the servicerequest may be triggered by the network, and/or the SMF 160 may removethe old (intermediate) UPF 110-2, the SMF 160 may send the N4 sessionmodification request message to the old (intermediate) UPF 110-2, andmay provide the DL tunnel information for the buffered DL data. If theSMF 160 may allocate new I-UPF 110, the DL tunnel information is fromthe new (intermediate) UPF 110 may act as N3 terminating point. If theSMF 160 may not allocate a new I-UPF 110, the DL tunnel information maybe from the new UPF 110 (PSA) 110-3 acting as N3 terminating point. TheSMF 160 may start a timer to monitor the forwarding tunnel. In anexample, the old (intermediate) UPF 110-2 may send N4 sessionmodification response message to the SMF 160.

In an example, if the I-UPF 110-2 may be relocated and forwarding tunnelwas established to the new I-UPF 110, the old (intermediate) UPF 110-2may forward its buffered data to the new (intermediate) UPF 110 actingas N3 terminating point. In an example, if the old I-UPF 110-2 may beremoved and the new I-UPF 110 may not be assigned for the PDU sessionand forwarding tunnel may be established to the UPF 110 (PSA) 110-3, theold (intermediate) UPF 110-2 may forward its buffered data to the UPF110 (PSA) 110-3 acting as N3 terminating point.

In an example, the SMF 160 may send to the AMF 155 an N11 message 1060e.g., a Nsmf_PDUSession_UpdateSMContext response (comprising: N1 SMcontainer (PDU session ID, PDU session re-establishment indication), N2SM information (PDU session ID, QoS profile, CN N3 tunnel info,S-NSSAI), Cause), upon reception of the Nsmf_PDUSession_UpdateSMContextrequest with a cause including e.g., establishment of user planeresources. The SMF 160 may determine whether UPF 110 reallocation may beperformed, based on the UE 100 location information, UPF 110 servicearea and operator policies. In an example, for a PDU session that theSMF 160 may determine to be served by the current UPF 110, e.g., PDUsession anchor or intermediate UPF, the SMF 160 may generate N2 SMinformation and may send an Nsmf_PDUSession_UpdateSMContext response1060 to the AMF 155 to establish the user plane(s). The N2 SMinformation may contain information that the AMF 155 may provide to theRAN 105. In an example, for a PDU session that the SMF 160 may determineas requiring a UPF 110 relocation for PDU session anchor UPF, the SMF160 may reject the activation of UP of the PDU session by sendingNsmf_PDUSession_UpdateSMContext response that may contain N1 SMcontainer to the UE 100 via the AMF 155. The N1 SM container may includethe corresponding PDU session ID and PDU session re-establishmentindication.

Upon reception of the Namf_EventExposure_Notify from the AMF 155 to theSMF 160, with an indication that the UE 100 is reachable, if the SMF 160may have pending DL data, the SMF 160 may invoke theNamf_Communication_N1N2MessageTransfer service operation to the AMF 155to establish the user plane(s) for the PDU sessions. In an example, theSMF 160 may resume sending DL data notifications to the AMF 155 in caseof DL data.

In an example, the SMF 160 may send a message to the AMF 155 to rejectthe activation of UP of the PDU session by including a cause in theNsmf_PDUSession_UpdateSMContext response if the PDU session maycorrespond to a LADN and the UE 100 may be outside the area ofavailability of the LADN, or if the AMF 155 may notify the SMF 160 thatthe UE 100 may be reachable for regulatory prioritized service, and thePDU session to be activated may not for a regulatory prioritizedservice; or if the SMF 160 may decide to perform PSA UPF 110-3relocation for the requested PDU session.

In an example, the AMF 155 may send to the (R)AN 105 an N2 requestmessage 1065 (e.g., N2 SM information received from SMF 160, securitycontext, AMF 155 signaling connection ID, handover restriction list, MMNAS service accept, list of recommended cells/TAs/NG-RAN nodeidentifiers). In an example, the RAN 105 may store the security context,AMF 155 signaling connection Id, QoS information for the QoS flows ofthe PDU sessions that may be activated and N3 tunnel IDs in the UE 100RAN 105 context. In an example, the MM NAS service accept may includePDU session status in the AMF 155. If the activation of UP of a PDUsession may be rejected by the SMF 160, the MM NAS service accept mayinclude the PDU session ID and the reason why the user plane resourcesmay not be activated (e.g. LADN not available). Local PDU sessionrelease during the session request procedure may be indicated to the UE100 via the session Status.

In an example, if there are multiple PDU sessions that may involvemultiple SMF 160 s, the AMF 155 may not wait for responses from all SMF160 s before it may send N2 SM information to the UE 100. The AMF 155may wait for all responses from the SMF 160 s before it may send MM NASservice accept message to the UE 100.

In an example, the AMF 155 may include at least one N2 SM informationfrom the SMF 160 if the procedure may be triggered for PDU session userplane activation. AMF 155 may send additional N2 SM information from SMF160 s in separate N2 message(s) (e.g. N2 tunnel setup request), if thereis any. Alternatively, if multiple SMF 160 s may be involved, the AMF155 may send one N2 request message to (R)AN 105 after all theNsmf_PDUSession_UpdateSMContext response service operations from all theSMF 160 s associated with the UE 100 may be received. In such case, theN2 request message may include the N2 SM information received in each ofthe Nsmf_PDUSession_UpdateSMContext response and PDU session ID toenable AMF 155 to associate responses to relevant SMF 160.

In an example, if the RAN 105 (e.g., NG RAN) node may provide the listof recommended cells/TAs/NG-RAN node identifiers during the AN releaseprocedure, the AMF 155 may include the information from the list in theN2 request. The RAN 105 may use this information to allocate the RAN 105notification area when the RAN 105 may decide to enable RRC inactivestate for the UE 100.

If the AMF 155 may receive an indication, from the SMF 160 during a PDUsession establishment procedure that the UE 100 may be using a PDUsession related to latency sensitive services, for any of the PDUsessions established for the UE 100 and the AMF 155 has received anindication from the UE 100 that may support the CM-CONNECTED with RRCinactive state, then the AMF 155 may include the UE's RRC inactiveassistance information. In an example, the AMF 155 based on networkconfiguration, may include the UE's RRC inactive assistance information.

In an example, the (R)AN 105 may send to the UE 100 a message to performRRC connection reconfiguration 1070 with the UE 100 depending on the QoSinformation for all the QoS flows of the PDU sessions whose UPconnections may be activated and data radio bearers. In an example, theuser plane security may be established.

In an example, if the N2 request may include a MM NAS service acceptmessage, the RAN 105 may forward the MM NAS service accept to the UE100. The UE 100 may locally delete context of PDU sessions that may notbe available in 5GC.

In an example, if the N1 SM information may be transmitted to the UE 100and may indicate that some PDU session(s) may be re-established, the UE100 may initiate PDU session re-establishment for the PDU session(s)that may be re-established after the service request procedure may becomplete.

In an example, after the user plane radio resources may be setup, theuplink data from the UE 100 may be forwarded to the RAN 105. The RAN 105(e.g., NG-RAN) may send the uplink data to the UPF 110 address andtunnel ID provided.

In an example, the (R)AN 105 may send to the AMF 155 an N2 request Ack1105 (e.g., N2 SM information (comprising: AN tunnel info, list ofaccepted QoS flows for the PDU sessions whose UP connections areactivated, list of rejected QoS flows for the PDU sessions whose UPconnections are activated)). In an example, the N2 request message mayinclude N2 SM information(s), e.g. AN tunnel info. RAN 105 may respondN2 SM information with separate N2 message (e.g. N2 tunnel setupresponse). In an example, if multiple N2 SM information are included inthe N2 request message, the N2 request Ack may include multiple N2 SMinformation and information to enable the AMF 155 to associate theresponses to relevant SMF 160.

In an example, the AMF 155 may send to the SMF 160 aNsmf_PDUSession_UpdateSMContext request 1110 (N2 SM information (ANtunnel info), RAT type) per PDU session. If the AMF 155 may receive N2SM information (one or multiple) from the RAN 105, then the AMF 155 mayforward the N2 SM information to the relevant SMF 160. If the UE 100time zone may change compared to the last reported UE 100 Time Zone thenthe AMF 155 may include the UE 100 time zone IE in theNsmf_PDUSession_UpdateSMContext request message.

In an example, if dynamic PCC is deployed, the SMF 160 may initiatenotification about new location information to the PCF 135 (ifsubscribed) by invoking an event exposure notification operation (e.g.,a Nsmf_EventExposure_Notify service operation). The PCF 135 may provideupdated policies by invoking a policy control update notificationmessage 1115 (e.g., a Npcf_SMPolicyControl_UpdateNotify operation).

In an example, if the SMF 160 may select a new UPF 110 to act asintermediate UPF 110 for the PDU session, the SMF 160 may initiates anN4 session modification procedure 1120 to the new I-UPF 110 and mayprovide AN tunnel info. The downlink data from the new I-UPF 110 may beforwarded to RAN 105 and UE 100. In an example, the UPF 110 may send tothe SMF 160, an N4 session modification response 1120. In an example,the SMF 160 may send to the AMF 155, a Nsmf_PDUSession_UpdateSMContextresponse 1140.

In an example, if forwarding tunnel may be established to the new I-UPF110 and if the timer SMF 160 set for forwarding tunnel may be expired,the SMF 160 may sends N4 session modification request 1145 to new(intermediate) UPF 110 acting as N3 terminating point to release theforwarding tunnel. In an example, the new (intermediate) UPF 110 maysend to the SMF 160 an N4 session modification response 1145. In anexample, the SMF 160 may send to the PSA UPF 110-3 an N4 sessionmodification request 1150, or N4 session release request. In an example,if the SMF 160 may continue using the old UPF 110-2, the SMF 160 maysend an N4 session modification request 1155, providing AN tunnel info.In an example, if the SMF 160 may select a new UPF 110 to act asintermediate UPF 110, and the old UPF 110-2 may not be PSA UPF 110-3,the SMF 160 may initiate resource release, after timer expires, bysending an N4 session release request (release cause) to the oldintermediate UPF 110-2.

In an example, the old intermediate UPF 110-2 may send to the SMF 160 anN4 session modification response or N4 session release response 1155.The old UPF 110-2 may acknowledge with the N4 session modificationresponse or N4 session release response message to confirm themodification or release of resources. The AMF 155 may invoke theNamf_EventExposure_Notify service operation to notify the mobilityrelated events, after this procedure may complete, towards the NFs thatmay have subscribed for the events. In an example, the AMF 155 mayinvoke the Namf_EventExposure_Notify towards the SMF 160 if the SMF 160had subscribed for UE 100 moving into or out of area of interest and ifthe UE's current location may indicate that it may be moving into ormoving outside of the area of interest subscribed, or if the SMF 160 hadsubscribed for LADN DNN and if the UE 100 may be moving into or outsideof an area where the LADN is available, or if the UE 100 may be in MICOmode and the AMF 155 had notified an SMF 160 of the UE 100 beingunreachable and that SMF 160 may not send DL data notifications to theAMF 155, and the AMF 155 may informs the SMF 160 that the UE 100 isreachable, or if the SMF 160 had subscribed for UE 100 reachabilitystatus, then the AMF 155 may notify the UE 100 reachability.

An example PDU session establishment procedure depicted in FIG. 12 andFIG. 13. In an example embodiment, when the PDU session establishmentprocedure may be employed, the UE 100 may send to the AMF 155 a NASMessage 1205 (or a SM NAS message) comprising NSSAI, S-NSSAI (e.g.,requested S-NSSAI, allowed S-NSSAI, subscribed S-NSSAI, and/or thelike), DNN, PDU session ID, request type, old PDU session ID, N1 SMcontainer (PDU session establishment request), and/or the like. In anexample, the UE 100, in order to establish a new PDU session, maygenerate a new PDU session ID. In an example, when emergency service maybe required and an emergency PDU session may not already be established,the UE 100 may initiate the UE 100 requested PDU session establishmentprocedure with a request type indicating emergency request. In anexample, the UE 100 may initiate the UE 100 requested PDU sessionestablishment procedure by the transmission of the NAS messagecontaining a PDU session establishment request within the N1 SMcontainer. The PDU session establishment request may include a PDU type,SSC mode, protocol configuration options, and/or the like. In anexample, the request type may indicate initial request if the PDUsession establishment is a request to establish the new PDU session andmay indicate existing PDU session if the request refers to an existingPDU session between 3GPP access and non-3GPP access or to an existingPDN connection in EPC. In an example, the request type may indicateemergency request if the PDU session establishment may be a request toestablish a PDU session for emergency services. The request type mayindicate existing emergency PDU session if the request refers to anexisting PDU session for emergency services between 3GPP access andnon-3GPP access. In an example, the NAS message sent by the UE 100 maybe encapsulated by the AN in a N2 message towards the AMF 155 that mayinclude user location information and access technology typeinformation. In an example, the PDU session establishment requestmessage may contain SM PDU DN request container containing informationfor the PDU session authorization by the external DN. In an example, ifthe procedure may be triggered for SSC mode 3 operation, the UE 100 mayinclude the old PDU session ID which may indicate the PDU session ID ofthe on-going PDU session to be released, in the NAS message. The old PDUsession ID may be an optional parameter which may be included in thiscase. In an example, the AMF 155 may receive from the AN the NAS message(e.g., NAS SM message) together with user location information (e.g.cell ID in case of the RAN 105). In an example, the UE 100 may nottrigger a PDU session establishment for a PDU session corresponding to aLADN when the UE 100 is outside the area of availability of the LADN.

In an example, the AMF 155 may determine that the NAS message or the SMNAS message may correspond to the request for the new PDU session basedon that request type indicates initial request and that the PDU sessionID may not be used for any existing PDU session(s) of the UE 100. If theNAS message does not contain an S-NSSAI, the AMF 155 may determine adefault S-NSSAI for the requested PDU session either according to the UE100 subscription, if it may contain only one default S-NSSAI, or basedon operator policy. In an example, the AMF 155 may perform SMF 160selection 1210 and select an SMF 160. If the request type may indicateinitial request or the request may be due to handover from EPS, the AMF155 may store an association of the S-NSSAI, the PDU session ID and aSMF 160 ID. In an example, if the request type is initial request and ifthe old PDU session ID indicating the existing PDU session may becontained in the message, the AMF 155 may select the SMF 160 and maystore an association of the new PDU session ID and the selected SMF 160ID.

In an example, the AMF 155 may send to the SMF 160, an N11 message 1215,e.g., Nsmf_PDUSession_CreateSMContext request (comprising: SUPI or PEI,DNN, S-NSSAI, PDU session ID, AMF 155 ID, request type, N1 SM container(PDU session establishment request), user location information, accesstype, PEI, GPSI), or Nsmf_PDUSession_UpdateSMContext request (SUPI, DNN,S-NSSAI, PDU session ID, AMF 155 ID, request type, N1 SM container (PDUsession establishment request), user location information, access type,RAT type, PEI). In an example, if the AMF 155 may not have anassociation with the SMF 160 for the PDU session ID provided by the UE100 (e.g. when request type indicates initial request), the AMF 155 mayinvoke the Nsmf_PDUSession_CreateSMContext request, but if the AMF 155already has an association with an SMF 160 for the PDU session IDprovided by the UE 100 (e.g. when request type indicates existing PDUsession), the AMF 155 may invoke the Nsmf_PDUSession_UpdateSMContextrequest. In an example, the AMF 155 ID may be the UE's GUAMI whichuniquely identifies the AMF 155 serving the UE 100. The AMF 155 mayforward the PDU session ID together with the N1 SM container containingthe PDU session establishment request received from the UE 100. The AMF155 may provide the PEI instead of the SUPI when the UE 100 hasregistered for emergency services without providing the SUPI. In casethe UE 100 has registered for emergency services but has not beenauthenticated, the AMF 155 may indicate that the SUPI has not beenauthenticated.

In an example, if the request type may indicate neither emergencyrequest nor existing emergency PDU session and, if the SMF 160 has notyet registered and subscription data may not be available, the SMF 160may register with the UDM 140, and may retrieve subscription data 1225and subscribes to be notified when subscription data may be modified. Inan example, if the request type may indicate existing PDU session orexisting emergency PDU session, the SMF 160 may determine that therequest may be due to handover between 3GPP access and non-3GPP accessor due to handover from EPS. The SMF 160 may identify the existing PDUsession based on the PDU session ID. The SMF 160 may not create a new SMcontext but instead may update the existing SM context and may providethe representation of the updated SM context to the AMF 155 in theresponse. if the request type may be initial request and if the old PDUsession ID may be included in Nsmf_PDUSession_CreateSMContext request,the SMF 160 may identify the existing PDU session to be released basedon the old PDU session ID.

In an example, the SMF 160 may send to the AMF 155, the N11 messageresponse 1220, e.g., either a PDU session create/update response,Nsmf_PDUSession_CreateSMContext response 1220 (cause, SM context ID orN1 SM container (PDU session reject(cause))) or anNsmf_PDUSession_UpdateSMContext response.

In an example, if the SMF 160 may perform secondaryauthorization/authentication 1230 during the establishment of the PDUsession by a DN-AAA server, the SMF 160 may select a UPF 110 and maytrigger a PDU session establishment authentication/authorization.

In an example, if the request type may indicate initial request, the SMF160 may select an SSC mode for the PDU session. The SMF 160 may selectone or more UPFs as needed. In case of PDU type IPv4 or IPv6, the SMF160 may allocate an IP address/prefix for the PDU session. In case ofPDU type IPv6, the SMF 160 may allocate an interface identifier to theUE 100 for the UE 100 to build its link-local address. For UnstructuredPDU type the SMF 160 may allocate an IPv6 prefix for the PDU session andN6 point-to-point tunneling (based on UDP/IPv6).

In an example, if dynamic PCC is deployed, the may SMF 160 performs PCF135 selection 1235. If the request type indicates existing PDU sessionor existing emergency PDU session, the SMF 160 may use the PCF 135already selected for the PDU session. If dynamic PCC is not deployed,the SMF 160 may apply local policy.

In an example, the SMF 160 may perform a session management policyestablishment procedure 1240 to establish a PDU session with the PCF 135and may get the default PCC Rules for the PDU session. The GPSI may beincluded if available at the SMF 160. If the request type in 1215indicates existing PDU session, the SMF 160 may notify an eventpreviously subscribed by the PCF 135 by a session management policymodification procedure and the PCF 135 may update policy information inthe SMF 160. The PCF 135 may provide authorized session-AMBR and theauthorized 5QI and ARP to SMF 160. The PCF 135 may subscribe to the IPallocation/release event in the SMF 160 (and may subscribe otherevents).

In an example, the PCF 135, based on the emergency DNN, may set the ARPof the PCC rules to a value that may be reserved for emergency services.

In an example, if the request type in 1215 indicates initial request,the SMF 160 may select an SSC mode for the PDU session. The SMF 160 mayselect 1245 one or more UPFs as needed. In case of PDU type IPv4 orIPv6, the SMF 160 may allocate an IP address/prefix for the PDU session.In case of PDU type IPv6, the SMF 160 may allocate an interfaceidentifier to the UE 100 for the UE 100 to build its link-local address.For unstructured PDU type the SMF 160 may allocate an IPv6 prefix forthe PDU session and N6 point-to-point tunneling (e.g., based onUDP/IPv6). In an example, for Ethernet PDU type PDU session, neither aMAC nor an IP address may be allocated by the SMF 160 to the UE 100 forthis PDU session.

In an example, if the request type in 1215 is existing PDU session, theSMF 160 may maintain the same IP address/prefix that may be allocated tothe UE 100 in the source network.

In an example, if the request type in 1215 indicates existing PDUsession referring to an existing PDU session moved between 3GPP accessand non-3GPP access, the SMF 160 may maintain the SSC mode of the PDUsession, e.g., the current PDU session Anchor and IP address. In anexample, the SMF 160 may trigger e.g. new intermediate UPF 110 insertionor allocation of a new UPF 110. In an example, if the request typeindicates emergency request, the SMF 160 may select 1245 the UPF 110 andmay select SSC mode 1.

In an example, the SMF 160 may perform a session management policymodification 1250 procedure to report some event to the PCF 135 that haspreviously subscribed. If request type is initial request and dynamicPCC is deployed and PDU type is IPv4 or IPv6, the SMF 160 may notify thePCF 135 (that has previously subscribed) with the allocated UE 100 IPaddress/prefix.

In an example, the PCF 135 may provide updated policies to the SMF 160.The PCF 135 may provide authorized session-AMBR and the authorized 5QIand ARP to the SMF 160.

In an example, if request type indicates initial request, the SMF 160may initiate an N4 session establishment procedure 1255 with theselected UPF 110. The SMF 160 may initiate an N4 session modificationprocedure with the selected UPF 110. In an example, the SMF 160 may sendan N4 session establishment/modification request 1255 to the UPF 110 andmay provide packet detection, enforcement, reporting rules, and/or thelike to be installed on the UPF 110 for this PDU session. If CN tunnelinfo is allocated by the SMF 160, the CN tunnel info may be provided tothe UPF 110. If the selective user plane deactivation is required forthis PDU session, the SMF 160 may determine the Inactivity Timer and mayprovide it to the UPF 110. In an example, the UPF 110 may acknowledgesby sending an N4 session establishment/modification response 1255. If CNtunnel info is allocated by the UPF, the CN tunnel info may be providedto SMF 160. In an example, if multiple UPFs are selected for the PDUsession, the SMF 160 may initiate N4 session establishment/modificationprocedure 1255 with each UPF 110 of the PDU session.

In an example, the SMF 160 may send to the AMF 155 anNamf_Communication_N1N2MessageTransfer 1305 message (comprising PDUsession ID, access type, N2 SM information (PDU session ID, QFI(s), QoSprofile(s), CN tunnel info, S-NSSAI, session-AMBR, PDU session type,and/or the like), N1 SM container (PDU session establishment accept (QoSRule(s), selected SSC mode, S-NSSAI, allocated IPv4 address, interfaceidentifier, session-AMBR, selected PDU session type, and/or the like))).In case of multiple UPFs are used for the PDU session, the CN tunnelinfo may comprise tunnel information related with the UPF 110 thatterminates N3. In an example, the N2 SM information may carryinformation that the AMF 155 may forward to the (R)AN 105 (e.g., the CNtunnel info corresponding to the core network address of the N3 tunnelcorresponding to the PDU session, one or multiple QoS profiles and thecorresponding QFIs may be provided to the (R)AN 105, the PDU session IDmay be used by AN signaling with the UE 100 to indicate to the UE 100the association between AN resources and a PDU session for the UE 100,and/or the like). In an example, a PDU session may be associated to anS-NSSAI and a DNN. In an example, the N1 SM container may contain thePDU session establishment accept that the AMF 155 may provide to the UE100. In an example, multiple QoS rules and QoS profiles may be includedin the PDU session establishment accept within the N1 SM and in the N2SM information. In an example, theNamf_Communication_N1N2MessageTransfer 1305 may further comprise the PDUsession ID and information allowing the AMF 155 to know which accesstowards the UE 100 to use.

In an example, the AMF 155 may send to the (R)AN 105 an N2 PDU sessionrequest 1310 (comprising N2 SM information, NAS message (PDU session ID,N1 SM container (PDU session establishment accept, and/or the like))).In an example, the AMF 155 may send the NAS message 1310 that maycomprise PDU session ID and PDU session establishment accept targeted tothe UE 100 and the N2 SM information received from the SMF 160 withinthe N2 PDU session request 1310 to the (R)AN 105.

In an example, the (R)AN 105 may issue AN specific signaling exchange1315 with the UE 100 that may be related with the information receivedfrom SMF 160. In an example, in case of a 3GPP RAN 105, an RRCconnection reconfiguration procedure may take place with the UE 100 toestablish the necessary RAN 105 resources related to the QoS Rules forthe PDU session request 1310. In an example, (R)AN 105 may allocate(R)AN 105 N3 tunnel information for the PDU session. In case of dualconnectivity, the master RAN 105 node may assign some (zero or more)QFIs to be setup to a master RAN 105 node and others to the secondaryRAN 105 node. The AN tunnel info may comprise a tunnel endpoint for eachinvolved RAN 105 node, and the QFIs assigned to each tunnel endpoint. AQFI may be assigned to either the master RAN 105 node or the secondaryRAN 105 node. In an example, (R)AN 105 may forward the NAS message 1310(PDU session ID, N1 SM container (PDU session establishment accept)) tothe UE 100. The (R)AN 105 may provide the NAS message to the UE 100 ifthe necessary RAN 105 resources are established and the allocation of(R)AN 105 tunnel information are successful.

In an example, the N2 PDU session response 1320 may comprise a PDUsession ID, cause, N2 SM information (PDU session ID, AN tunnel info,list of accepted/rejected QFI(s)), and/or the like. In an example, theAN tunnel info may correspond to the access network address of the N3tunnel corresponding to the PDU session.

In an example, the AMF 155 may forward the N2 SM information receivedfrom (R)AN 105 to the SMF 160 via a Nsmf_PDUSession_UpdateSMContextrequest 1330 (comprising: N2 SM information, request type, and/or thelike). In an example, if the list of rejected QFI(s) is included in N2SM information, the SMF 160 may release the rejected QFI(s) associatedQoS profiles.

In an example, the SMF 160 may initiate an N4 session modificationprocedure 1335 with the UPF 110. The SMF 160 may provide AN tunnel infoto the UPF 110 as well as the corresponding forwarding rules. In anexample, the UPF 110 may provide an N4 session modification response1335 to the SMF 160160.

In an example, the SMF 160 may send to the AMF 155 aNsmf_PDUSession_UpdateSMContext response 1340 (Cause). In an example,the SMF 160 may subscribe to the UE 100 mobility event notification fromthe AMF 155 (e.g. location reporting, UE 100 moving into or out of areaof interest), after this step by invoking Namf_EventExposure_Subscribeservice operation. For LADN, the SMF 160 may subscribe to the UE 100moving into or out of LADN service area event notification by providingthe LADN DNN as an indicator for the area of interest. The AMF 155 mayforward relevant events subscribed by the SMF 160.

In an example, the SMF 160 may send to the AMF 155, aNsmf_PDUSession_SMContextStatusNotify (release) 1345. In an example, ifduring the procedure, any time the PDU session establishment is notsuccessful, the SMF 160 may inform the AMF 155 by invokingNsmf_PDUSession_SMContextStatusNotify(release) 1345. The SMF 160 mayreleases any N4 session(s) created, any PDU session address if allocated(e.g. IP address) and may release the association with the PCF 135.

In an example, in case of PDU type IPv6, the SMF 160 may generate anIPv6 Router Advertisement 1350 and may send it to the UE 100 via N4 andthe UPF 110.

In an example, if the PDU session may not be established, the SMF 160may unsubscribe 1360 to the modifications of session managementsubscription data for the corresponding (SUPI, DNN, S-NSSAI), usingNudm_SDM_Unsubscribe (SUPI, DNN, S-NSSAI), if the SMF 160 is no morehandling a PDU session of the UE 100 for this (DNN, S-NSSAI). In anexample, if the PDU session may not be established, the SMF 160 mayderegister 1360 for the given PDU session using Nudm_UECM_Deregistration(SUPI, DNN, PDU session ID).

As depicted in FIG. 14, a connection management (CM) state may berelated to a radio resource control (RRC) state. RRC-INACTIVE (e.g. RRCinactive) may be a state where a UE (e.g. a wireless device, device)remains in CM-CONNECTED (e.g. CM connected). In an example, the UE maymove within an area configured by a RAN (e.g. NG-RAN), referred to as aRAN notification area (RNA), without notifying the RAN. In RRC_INACTIVEstate, the last base station (e.g., gNB) of a RAN to serve the UE maykeep the UE context and the UE-associated connection with the servingAMF and UPF (e.g. N2 connection, N3 connection). In an example, a UE inCM-IDLE may be in RRC-IDLE. In an example, a UE in CM-CONNECTED may bein RRC-CONNECTED. The mobility behavior of the UE in RRC-INACTIVE may besimilar with RRC-IDLE state behavior (e.g. cell reselection based onserving cell quality, paging monitoring, periodic system informationacquisition) and may apply different parameter for RRC-IDLE andRRC-INACTIVE.

FIG. 15 illustrates an example call flow for four RRC state transitionsin accordance with embodiments of the present disclosure. The four RRCstate transitions include: RRC-IDLE to RRC-CONNECTED; RRC-CONNECTED toRRC-INACTIVE; RRC-INACTIVE to RRC-CONNECTED; and RRC_CONNECTED toRRC-IDLE. It should be noted that, although the four RRC statetransitions are shown as part of a single call flow diagram, each RRCstate transition call flow can be performed independently from eachother.

Starting with the RRC state transition from RRC-IDLE to RRC-CONNECTED, aUE in RRC-IDLE may send an RRC setup request message to an NG-RAN node(e.g., a gNB) to request RRC connection setup with the NG-RAN. The UEmay receive an RRC setup message from the NG-RAN node in response to theRRC setup request message. The UE may transition from the RRC-IDLE toRRC-CONNECTED in response to the RRC setup message from the NG-RAN node.The RRC state maintained at the UE may be updated to reflect that thecurrent RRC state of the UE is RRC-CONNECTED after the state transition.The UE may respond to the RRC setup message by sending an RRC setupcomplete message to the NG-RAN. The RRC state maintained at the NG-RANnode may be updated to reflect that the current RRC state of the UE isRRC-CONNECTED after receiving the RRC setup complete message.

For the RRC state transition from RRC-CONNECTED to RRC-INACTIVE, theNG-RAN node may send an RRC release message to the UE to requestsuspension of an RRC connection. In an example, the RRC release messagemay include suspend information that indicates to the UE that the RRCrelease message is for suspending instead of releasing the RRCconnection. The suspend information may comprise a radio networktemporary identity (RNTI) value, a radio access network (RAN) pagingcycle, RAN notification area information, and/or the like. The UE maytransition from RRC-CONNECTED to RRC-INACTIVE in response to the RRCrelease message from the NG-RAN node. The RRC state maintained at boththe UE and the NG-RAN node may be updated to reflect that the currentRRC state of the UE is RRC-INACTIVE.

For the RRC state transition from RRC-INACTIVE to RRC-CONNECTED, the UEmay send an RRC resume request message to the NG-RAN node to requestthat the suspended RRC connection be resumed. The UE may receive an RRCresume message from the NG-RAN node in response to the RRC resumerequest message. In response to the RRC resume message from the NG-RANnode, the UE may transition from RRC-INANCTIVE to RRC-CONNECTED stateand may send an RRC resume complete message to the NG-RAN node. The RRCstate maintained at the UE may be updated to reflect that the currentRRC state of the UE is RRC-CONNECTED after the state transition. The RRCstate maintained at the NG-RAN node may be updated to reflect that thecurrent RRC state of the UE is RRC-CONNECTED after receiving the RRCresume complete message from the UE.

Finally, for the RRC state transition from RRC-CONNECTED to RRC-IDLE,the NG-RAN node may send an RRC release message to the UE to requestthat the RRC connection be released. The UE may transition fromRRC-CONNECTED to RRC-IDLE after receiving RRC release message from theNG-RAN node. The RRC state maintained at both the UE and the NG-RAN nodemay be updated to reflect that the current RRC state of the UE isRRC-IDLE.

In an example, a unique international mobile subscription identity(IMSI), as shown in FIG. 21A, is a permanent UE identity and may beallocated and used in GSM/UMTS/EPS system. In an example, subscriptionpermanent identity (SUPI) may be a globally unique UE identity to eachsubscriber in a 5G system and SUPI may be the IMSI.

In an example, a globally unique temporary UE identity (GUTI) may be toprovide an unambiguous identification of a UE that does not reveal theIMSI in evolved packet system (EPS) and may be used for an MME and anetwork.

In an example, a fifth generation globally unique temporary UE identity(5G-GUTI) may be to provide an unambiguous identification of a UE thatdoes not reveal the UE's permanent identity in 5G system (5GS) and maybe used for an AMF and a network.

FIG. 21B depicts an example structure of an EPS/4G UE identifiers. In anexample, mobile country code (MCC) may be consisted of three digits andmay identify uniquely the country of domicile of the mobilesubscription. In an example, mobile network code (MNC) may be consistedof two or three digits for 3GPP network application and the MNC mayidentify the home PLMN of the mobile subscription. In an example, theGUTI may be constructed from a globally unique MME identifier (GUMMEI)and M-TMSI. In an example, the GUMMEI may be constructed from the MCC,MNC and MME identifier (MMEI). In an example, MME code (MMEC) may beunique within the MME pool area and M-TMSI. In an example, a UE may beidentified by a M-TMSI within a MME. In an example, S-TMSI may beshortened from of the GUTI to enable more efficient radio signalingprocedure (e.g. paging and service request). The S-TMSI may beconstructed from the MMEC and the M-TMSI.

FIG. 21C depicts an example structure of a 5G UE identifiers. In anexample, mobile country code (MCC) may be consisted of three digits andmay identify uniquely the country of domicile of the mobilesubscription. In an example, mobile network code (MNC) may be consistedof two or three digits for 3GPP network application and the MNC mayidentify the home PLMN of the mobile subscription. In an example, the5G-GUTI may be constructed from a globally unique AMF identifier (GUAMI)and 5G-TMSI. In an example, the GUAMI may be constructed from the MCC,MNC and AMF identifier (AMFI). In an example, the AMFI may beconstructed from an AMF Region ID, an AMF Set ID and an AMF Pointer. TheAMF Region ID may identity the region, the AMF Set ID may uniquelyidentity the AMF Set within the AMF region, and the AMF Pointer mayidentity one or more AMFs within the AMF Set. In an example, 5G-S-TMSImay be shortened form of the 5G-GUTI and the 5G-S-TMSI may be used toefficient radio signaling procedures (e.g. paging and Service Request).

FIG. 16 illustrates a paging procedure from an AMF. In an example, a UEand an AMF may negotiate a UE specific DRX cycle via a registrationprocedure. In an example, radio connection and N2/N3 connection of theUE may be released and the UE may transition into CM-IDLE state. Ifthere is a terminating call towards a UE in CM-IDLE state, the AMF maysend paging messages over the N2 interface to relevant base stations(gNBs/eNBs) belonging to the tracking areas at which the UE is expectedto be placed. In an example, a UPF may receive downlink data for a PDUsession and there is no AN Tunnel info stored in the UPF for the PDUSession. The UPF may send a data notification message to a SMF inresponse to receiving the downlink data, requesting a user planeconnection setup for the PDU session with the UE. In an example, the SMFmay send a communication request message to the AMF in response toreceiving the data notification from the UPF, requesting a communicationsetup with the UE. The communication request message may be aNamf_Communication_N1N2MessageTransfer. In an example, the communicationrequest message may comprise UE identity, PDU session identity, sessionmanagement container, QFI, QoS profile, 5QI, ARP, PPI, N1 message and/orthe like. In an example, the paging message may comprise a pagingidentity of the paged UE and tracking areas for which the paged UE isexpected to be located. In an example, the paging message may be N2paging request message. The paging identity may indicate the UE identityrepresented in the form of either an 5G-TMSI/S-TMSI or IMSI. In anexample, the base station(s) may perform paging of the UE over the radiointerface (e.g. Uu interface) by sending paging messages on the cellsbelonging to the tracking areas indicted in the N2 paging message. In anexample, the paging message may comprise a list of paging records, whereeach paging record contains the paging identity of the paged UE.

From the UE side, to receive the paging message, the UE in CM-IDLE statemay be required to monitor a physical control channel, referred to as aphysical downlink control channel (PDCCH), masked by the paging-radionetwork temporary identity (P-RNTI), addressing the paging message, asshown in FIG. 18. In an example, the UE may monitor the PDCCH onparticular paging occasions (PO) for paging reception. The subframeswhere the paging message may be transmitted to the UE is defined by thepaging frame (PF) and the paging occasion (PO) within the PF, asdepicted in FIG. 18. The PF may comprise one or more PO(s). Theallocation PO(s) may be by utilizing the IMSI or 5G-S-TMSI of the pagedUEs such that the POs allocated to different UEs. A UE is in CM-IDLEstate may use DRX operation and it may need to monitor at least one POduring a paging DRX cycle.

When decoding the paging message, the UE may consider that it is beingpaged if its UE identity exists in the paging records(s). In an example,the UE may ignore a paging message that does not include its UE identityunless the paging message is used for other purposes, for example,system information change notification. In an example, the DRX intervalmay be 0.32 s, 0.42 s, 1.28 s, 2.56 s and/or the like.

FIG. 19A shows example DRX parameters of a UE for PF and PO for pagingmonitoring occasion calculation. A UE specific DRX cycle (i.e. Tue) maybe configured in the UE and provided by the UE during registrationprocedure to an AMF. In an example, the AMF may provide the UE specificDRX cycle for paging procedure to a base station. A cell specific DRXcycle (i.e. Tc) may be configured in the base station and may bebroadcasted by the base station. In an example, the UE and the basestation may use shortest DRX cycle among the UE specific DRX cycle andthe cell specific DRX cycle for a DRX cycle value for paging occasioncalculation.

FIG. 19B shows example input parameters for paging occasion calculationwhich may be used in FIG. 19C and FIG. 19D. In an example, the number ofpaging occasions per DRX cycle ‘nB’ may be configured by a base stationand may be broadcasted by the base station via system information.

The Paging message from the MME/AMF may contain the S-TMSI (4G) or the5G-S-TMSI (5G). The base station has to schedule the transmission ofpages over the air, since each UE only looks for them at a configuredinterval (usually every 1.28 or 2.56 seconds). The S-TMSIs/5G-S-TMSIs ofthe UEs that may be paged at a particular time are included in the samePaging message, and the base station may allocate the necessary downlink(PDSCH) resources to carry the message; a downlink control information(DCI) in the PDCCH pointing at those resources are associated with theP-RNTI, so that the UEs recognize that a Paging message is being sent,and therefore can decode it correctly.

FIG. 19C shows an example equation to derive a system frame number (SFN)for the paging frame for LTE/4G. Paging occasion of the paging frame maybe calculated using an equation i_s based on a subframe patterns in FIG.20A and FIG. 20B. In an example, the UE_ID may be the IMSI.

FIG. 19D shows an example equation to derive a system frame number (SFN)for the paging frame for new radio (NR) (e.g. 5G). The difference of theequation for paging frame of NR (5G) comparing to LTE/4G is anintroduction of new parameter PF_offset. The PF_offset may bebroadcasted by a base station using system information block 1 and cellspecific value. In an example, the UE_ID may be the 5G-S-TMSI.

FIG. 17 illustrates a paging procedure while a UE is in RRC-INACTIVEstate. In an example, a UE specific DRX cycle may be provided by the UEto the AMF during registration procedure. In an example, the AMF mayprovide a RAN paging related information during a context setupprocedure to establish a connection setup with the UE. In an example,the AMF may send a context setup request message comprising core networkassistance information. In an example, the core network assistanceinformation may comprise a registration area of the wireless device, aparameter indicating the MICO mode is allowed for the wireless device, aperiodic registration area update time value, UE specific DRX valuesand/or the like. In an example, the base station may send an RRC releasemessage comprising RRC suspension/suspend configuration information inresponse to determining UE inactivity for a period of time (e.g. thereis no transmission from or reception by the UE in 10 seconds). In anexample, the suspension/suspend configuration information may comprise aradio network temporary identity (RNTI), a radio access network (RAN)paging cycle, a RAN notification area (RNA) information, a periodic RNAupdate time value, and/or the like. In an example, the RAN notificationarea information may comprise a list of cells, a PLMN identity, a listof tracking area codes, a list of RAN area code, and/or the like. In anexample, the UE may perform a RAN notification area update procedure inresponse to entering a cell which does not belong to the RNA. In anexample, the UE may perform the RAN notification area update procedurein response to entering a new RNA. In an example, the base station maydetermine the periodic RNA update time value based on the periodicregistration area update time value. In an example, the periodic RNAupdate time value (e.g., 30 minutes or 1 hour) may be smaller than theperiodic registration area update time value (e.g., 3 hours or 12hours).

In an example, the base station may receive a user packet data from of aNAS PDU from core network node(s) for the UE. In an example, the basestation may receive a user packet data from a UPF. In an example, thebase station may receive a downlink NAS transport message comprising aNAS PDU from the AMF, as depicted in FIG. 17. In an example, the basestation may send the paging message, in response to receiving thedownlink PDU session information or the downlink NAS transport message.The calculation of a paging frame and paging occasion by the UE and thebase station may be similar as CM-IDLE state paging procedure asdescribed previously. The UE and the base station may use shortest DRXcycle among the RAN paging cycle value and the cell specific DRX cycleas a DRX cycle value ‘T’ for paging occasion calculation. The cellspecific DRX cycle (i.e. Tc) may be configured in the base station andmay be broadcasted by the base station. The RAN paging cycle may beprovided by the base station during RRC release procedure.

In an example, a UE may employ more than one subscriber identity module(SIM) as depicted in FIG. 22. The UE may further comprise communicationinterface(s), a speaker/microphone, a keypad, a display/touchpad,processor(s), a data base, a power source, a global positioning system(GPS) chipset, peripherals and/or the like. In an example, the UE mayfurther comprise a single transmitter and one or more receivers. In anexample, the UE may be a multi-SIM UE. In an example, the multi-SIM UEmay be a dual-SIM UE. The UE may register to different PLMNssimultaneously and may be prepared to place and receive voice calls onboth PLMN.

As depicted in FIG. 22, the UE may attempt to receive paging messagefrom wireless network 2 employing SIM 2, during the time period of theUE is in CM-CONNECTED state to wireless network 1 employing SIM 1. TheUE may create gaps on the active connection with wireless network 1 inorder to monitor/listen to paging of the other connection, the wirelessnetwork 2. In an example, the UE may not be reachable by the wirelessnetwork 1 during the time period of the gap.

FIG. 23 and FIG. 24 illustrates an example architecture with a dual-SIMUE and two wireless networks. In an example, FIG. 23 illustrates thecase that both data network/PLMN employing 5G system and FIG. 41illustrates the case that one data network/PLMN employs 4G network andthe other data network/PLMN employs 5G network.

As depicted in FIG. 23 and FIG. 24, the UE may simultaneouslycommunicate via a non-3GPP access of wireless network 2 during a timeperiod of that the UE actively communicate via 3GPP access of wirelessnetwork 1. In an example, the dual-SIM UE employing single transmissionfor 3GPP access may simultaneously activate non-3GPP transmission.

As depicted in FIG. 25, a dual-SIM UE may monitor paging messages from abase station of a PLMN 1 and a base station of PLMN 2 simultaneously. Inan example, the UE may employ a single or more receivers and singletransmitter. When the UE receives a paging message from the base stationof the PLMN 1, the UE may (depending on implementation andconfiguration) drop the (data) connection (if any) with the base stationof the PLMN 2.

In existing wireless technologies, a UE may need to monitor twodifferent paging messages from two different systems simultaneously. Foran example, a dual-SIM UE may monitor two different paging messages fromtwo different subscribed public land mobile networks (PLMNs). In anexample, the dual-SIM UE may comprise single receiver (Rx chain) so theUE may not be able to monitor/receive two different paging messagessimultaneously. In an example, the dual-SIM UE may comprise dualreceivers. The dual-SIM UE with dual receiver may employ a dualconnectivity or a carrier aggregation using dual receiver for onesubscription so the UE may not be able to monitor two different pagingmessages simultaneously. It may be possible that the paging monitoringoccasions for each subscriptions of the UE may occur around the sametime for the UE. It may result in paging collision between thesubscriptions, as depicted in FIG. 26A. In this case, the UE may be ableto receive a paging message of one subscription (e.g. PLMN 2) and the UEmay not be able to receive a paging message of the other subscription(e.g. PLMN 1). In an example, the paging collision may occur when thetime of paging occasion of each subscription is overlapped. In anexample, the paging collision may occur when the time of paging occasionof each subscription is not overlapped but there is not enough time forfrequency tuning between two PLMNs. In an example, two different PLMNsmay employ different frequencies so a UE may need to tune to differentfrequency. The frequency tuning (e.g. form frequency 1 of PLMN 1 tofrequency 2 of PLMN 2) may take a certain period of time. Missing pagingmessage due to paging collision may decrease a performance of a userexperience and it may decrease popularity of the dual-SIM UEs.

In an example embodiment, a UE may determine a need of paging adjustmentwith a serving PLMN. In an example, the determining may be based onpaging collision detection with other PLMN or other service in the samePLMN. In an example, the determining may be based on a need of powersaving of the UE to minimize a number of wake up for paging monitoringof one more subscription. The UE may send paging adjustment informationto an AMF during registration procedure and the AMF may determine pagingadjustment parameters based on the paging adjustment information for UEin CM-IDLE state. For RRC-INACTIVE case, the AMF may provide a corenetwork parameter for paging adjustment based on the paging adjustmentinformation to the base station during a context setup procedure. Thebase station may determine a parameter for a RAN paging adjustment basedon the core network parameter for paging adjustment and may send to theUE during radio resource control (RRC) suspension procedure. Embodimentsof the present disclosure may increase a performance of a userexperience by decreasing of paging collision occurrence of a UE inCM-IDLE state and in RRC-INACTIVE state. Embodiments of the presentdisclosure may increase power efficiency of the UE by allocating thepaging monitoring occasions of two different subscription in an adjacenttime to minimize the number of wake up for paging monitoring.

FIG. 28 illustrates an example embodiment of a paging adjustment requestprocedure between a UE and an AMF. FIG. 29 illustrates an exampleembodiment of a paging procedure for a UE in CM-IDLE after the pagingadjustment is negotiated. In an example, the UE may be a multi-SIMdevice. In an example, the UE may be dual-SIM device.

Referring to FIG. 28, the UE may be registered with an AMF of PLMN 2previously. In an example, the UE may read system information blocks ofa base station of a PLMN 1. In an example, the UE may determine anoccurrence of paging collision between PLMN 1 and PLMN 2. Thedetermination may be based on paging occasion calculation using theinformation in system information block 1. The UE may calculate a pagingframe and paging occasion based on the shortest paging DRX cycle betweena cell specific DRX in system information block 1 and a UE specific DRX.In an example, the UE may provide paging adjustment information duringinitial registration with the PLMN 1.

In an example, the UE may be registered previously with an AMF of PLMN 1and determine a need of paging adjustment with PLMN 1. In an example,the UE may perform registration update with the PLMN 1 by sendingregistration request message comprising paging adjustment information.

In response to the determining, the UE may send a registration requestmessage comprising the paging adjustment information, via a base stationto the AMF of the PLMN 1, requesting a registration with PLMN 1. In anexample, the registration request message may comprise a UE specificDRX, paging adjustment information, a UE identity (e.g., SUCI, 5G-GUTI),the location of the UE (e.g., last visited TAI), requested NSSAI, UEmobility management context information, PDU session state, informationfor the MICO mode usage, and/or the like.

In an example, the paging adjustment information may comprisenon-preferred system frame number(s) for paging, preferred system framenumber(s) for paging, a conflicted system frame number(s) for paging, arequested paging offset value represented as a system frame number, arequested paging offset value represented as a time period, a requestedpaging offset value represented as a UE identity, an indication thatpaging repetition is required, an indication that paging occasion isconflicted, a requested paging repetition number, non-preferredfrequency/band for paging, preferred frequency/band for paging, anindication that a UE specific discontinuous reception (DRX) beingpreferred and/or the like.

In an example, the non-preferred system frame number(s) for paging maybe system frame number(s) that the UE detected paging collision.

In an example, the preferred system frame number(s) for paging may besystem frame number(s) that the UE may prefer to monitor paging with thePLMN 1.

In an example, the conflicted system frame number(s) for paging may besystem frame number(s) that the UE detected paging collision.

In an example, the requested paging offset value represented as a systemframe number may be a number of radio frame(s) that the UE request toshift for paging monitoring. FIG. 27A shows example diagram for thepaging offset value.

In an example, the requested paging offset value represented as a timeperiod may be a time period that the UE request to shift for pagingmonitoring.

In an example, the requested paging offset value represented as a UEidentity may be used as an offset value to UE_ID in the equation in FIG.19C or FIG. 19D. In an example, the UE_ID in FIG. 19C and FIG. 19D maybe modified with the requested paging offset value represented as a UEidentity. In an example, the paging frame number and paging occasion maybe modified in response to using the requested paging offset. In anexample, the paging collision may be resolved by the paging offset forthe UE_ID.

In an example, the indication that paging repetition is required may beused by the AMF that paging retransmission is needed for this UE, asdepicted in FIG. 27B.

In an example, the indication that paging occasion is conflicted may beused by the AMF that paging occasion adjustment or modification isrequested.

In an example, the requested paging repetition number may be used by theAMF that paging retransmission is needed for this UE, as depicted inFIG. 27B.

In an example, the non-preferred frequency/band for paging may befrequency/band (s) that the UE used for communication or monitoring forother subscription (e.g. SIM 2 of PLMN 2). In an example, the UE mayindicate the non-preferred frequency/band if the UE wants to avoid usingwith PLMN 1.

In an example, the preferred frequency/band for paging may befrequency/band (s) that the UE wants to use with PLMN 1.

In an example, the UE may determine that the paging collision may beresolved if the UE using the UE specific DRX instead of the cellspecific DRX, as depicted in FIG. 27C. In this case the UE may indicatethe indication that a UE specific discontinuous reception (DRX) beingpreferred.

In an example, the AMF may determine whether to accept the request fromthe UE for the paging adjustment. The AMF may determine based on therequest for paging adjustment, a local policy of the AMF, subscriptioninformation of the UE in a UDM, an overload situation of a pagingresource of the system and/or the like. In an example, the AMF may notaccept the request if the local policy of the AMF does not allow it. Inan example, the AMF may not accept the request if the subscriptioninformation of the UE does not fulfill the paging adjustment for the UE.In an example, the AMF may not accept the paging adjustment request ifthe paging resource usage condition does not allow it.

In an example, the AMF may accept the paging adjustment request inresponse to the determination. The AMF may determine paging adjustmentparameters for the UE. In an example, the AMF may consult to the basestation to get the paging adjustment parameters for the pagingadjustment information. The AMF may send a registration accept messageto the UE indicating a successful registration. In an example, theregistration accept message may comprise 5G-GUTI, registration area, aperiodic registration area update time value, a MICO mode indication,paging adjustment parameters and/or the like.

In an example, the paging adjustment parameters may comprise a pagingtime offset comprising number of radio frames and/or number of radiosub-frames, a paging UE identity offset, frequency/band information forpaging, frequency/band information not used for paging, pagingrepetition number, an indication that a UE specific discontinuousreception (DRX) is prioritized and/or the like.

In an example, a paging frame (PF) based on the paging adjustmentparameter may be incremented with the paging time offset in response tothe paging adjustment parameter being the paging time offset. In anexample, the final PF of FIG. 19C may be system frame number (SFN) 38 inresponse to the initial PF is SFN 30 and the paging time offset is SFN8.

In an example, the paging time offset may be used to replace thePF_offset in the question of FIG. 19D. In an example, the PF_offset iscell specific paging offset value. In an example, the UE and the basestation may be used the paging time offset instead of the cell specificpaging offset ‘PF_offset’.

In an example, the UE_ID in FIG. 19C and FIG. 19D may be incrementedbased on the paging UE identity offset, in response to the pagingadjustment parameter being the paging UE identity offset. In an example,IMSI of the UE is ‘1234123412341234’ and the paging UE identity offsetis ‘1021’ then the UE_ID for calculation of the paging frame and thepaging occasion may be the IMSI (1234123412341234) plus the paging UEidentity offset (1021) and the UE_ID may be ‘12341234123412342255’.

In an example, the UE may monitor frequencies/bands for paging receptionin the frequency/band information for paging, in response to the pagingadjustment parameter being the frequency/band information for paging.

In an example, the UE may not monitor frequencies/bands for pagingreception in the frequency/band information not used for paging, inresponse to the paging adjustment parameter being the frequency/bandinformation not used for paging.

In an example, the UE may monitor consecutive system frame number forpaging, in response to the paging adjustment parameter being the pagingrepetition number. In an example, the calculated paging frame usingquestion 19.C and 19.C is SFN 34 and the paging repetition number is 2,then the UE may monitor the system frame number 34, 35, 36 for pagingreception.

In an example, the UE may use the UE specific discontinuous reception(DRX) value instead of a default DRX value of the base station, inresponse to the paging adjustment parameters being the indication that aUE specific discontinuous reception (DRX) is prioritized. In an example,the T value of the FIG. 19B is Tue. In an example, the UE may not employmin (Tue, Tc) condition in response to the paging adjustment parametersbeing the indication that a UE specific discontinuous reception (DRX) isprioritized.

In an example, the AMF and the base station may determine a connectionrelease with the UE. In an example, the determination of the connectionrelease with the UE may be based on UE inactivity detection for a periodof time (e.g. there is no transmission from or reception by the UE in 10seconds). In an example, the UE may enter in an CM-IDLE state from aCM-CONNECTED state in response to a completion of a connection release.In an example, the completion of the connection release may be receivingan RRC release message from the base station. In an example, the UEstate in the AMF may change to CM-IDLE state from the CM-CONNECTEDstate.

Now referring to FIG. 29, the UE may monitor paging messages based onthe paging adjustment parameters and the network may send pagingmessages based on the paging adjustment parameters. The UE may determinepaging occasion (e.g. PF, PO) based on the paging adjustment parameters,broadcasted system information by the base station, a UE specific DRXand/or the like.

In an example, a paging procedure may be triggered by the AMF of thePLMN 1, in response to an occurrence of a network triggered servicerequest. In an example, the network triggered service request may betriggered by a UPF in response to receiving downlink data. In anexample, the network triggered service request may be triggered by somenetwork functions (e.g. NEF, SMSF, PCF) to request a delivery of controlsignaling for the UE. In an example, PCF may request the networktriggered service request due to change of a UE policy. In an example,the network triggered service request may be triggered by the AMFitself, due to a change of UE configuration (e.g. MICO disabling, sliceinformation update).

In an example, the AMF may send paging messages over the N2 interface torelevant base stations (gNBs) belonging to the tracking areas at whichthe UE is expected to be placed. In an example, the paging message maybe N2 paging request message. In an example, the paging message maycomprise UE identity, an access type, UE specific DRX, area informationfor paging, paging adjustment parameters and/or the like. In an example,the UE identity may indicate 5G S-TMSI. In an example, the access typemay indicate a third-generation partnership project (3GPP) accesstechnology. In an example, the area information may comprise a list ofcell identities for paging. In an example, the UE specific DRX may bepreviously negotiated DRX value between the UE and the AMF in recentregistration procedure. The paging adjustment parameters may comprise apaging time offset comprising number of radio frames and/or number ofradio sub-frames, a paging UE identity offset, frequency/bandinformation for paging, frequency/and information not used for paging,paging repetition number, an indication that a UE specific discontinuousreception (DRX) is prioritized and/or the like. In an example, the basestation may use the paging adjustment parameter for paging frame andpaging occasion calculation for the UE.

In an example, the UE may receive the paging message successfully. TheUE may determine to send a radio resource control (RRC) message torequest a connection setup with the PLMN 1 in response to receiving thepaging message.

In an example, the UE may receive an RRC request response message inresponse sending the RRC request message. The UE may send an RRC requestcomplete message to the base station. The RRC request complete messagemay comprise a NAS service request message. After this, the UE triggeredservice request procedure may be invoked as described in FIG. 10 andFIG. 11.

FIG. 30 illustrates a paging procedure for a UE inCM-CONNECTED/RRC-INACTIVE after the paging adjustment is negotiated asexplained FIG. 28 description.

Referring to FIG. 28, the UE may determine an occurrence of pagingcollision between PLMN 1 and PLMN 2. In an example, the UE may providepaging adjustment information during registration procedure with thePLMN 1, in response to the determining of the paging collision. In anexample, the AMF may determine a paging adjustment parameter in responseto the paging adjustment information successfully as explained in FIG.28. For the CM-CONNECTED/RRC-INACTIVE case, the release procedure of theFIG. 28 may be skipped.

Now referring to FIG. 30, a service request procedure, as shown in FIG.10 and FIG. 11, may be performed between the UE and the network of thePLMN 1. In an example, the AMF may send a context setup request messageto the base station as part of the service request procedure. In anexample, the context setup request message may be an initial contextsetup request message. In an example, the context setup request messagemay be a UE context modification request message. In an example, thecontext setup request message may comprise a parameter indicating MICOmode is allowed/accepted for the UE, AMF UE NGAP ID, RAN UE NGAP ID, oldAMF address, UE aggregate maximum bit rate, PDU session information forsetup, and/or the like. In an example, the AMF UE NGAP ID may uniquelyidentify a UE association over the NG interface (e.g. N2 interface)within the AMF side. The RAN UE NGAP ID may uniquely identify a UEassociation over the NG interface within the NG-RAN side. In an example,the context setup request message may further comprise a core networkparameter for paging adjustment in response to the paging adjustmentnegotiation.

In an example, the core network parameter for paging may comprisenon-preferred system frame number for paging, preferred system framenumber for paging, a conflicted system frame number for paging, arequested paging offset value represented as a system frame number, arequested paging offset value represented as a time period, a requestedpaging offset value represented as a UE identity, an indication thatpaging repetition is required, an indication that paging occasion isconflicted, a requested paging repetition number, non-preferredfrequency/band for paging, preferred frequency/band for paging, anindication that a UE specific discontinuous reception (DRX) beingpreferred and/or the like. In an example, the base station may determinea parameter for RAN paging adjustment based on the core networkparameter for paging. In an example, the parameter for RAN pagingadjustment may comprise a paging time offset comprising number of radioframes and/or number of radio sub-frames, a paging UE identity offset,frequency/band information for paging, frequency/and information notused for paging, paging repetition number, an indication that a UEspecific discontinuous reception (DRX) is prioritized and/or the like.

In an example, the core network parameter for paging may comprise apaging time offset comprising number of radio frames and/or number ofradio sub-frames, a paging UE identity offset, frequency/bandinformation for paging, frequency/and information not used for paging,paging repetition number, an indication that a UE specific discontinuousreception (DRX) is prioritized and/or the like. In an example, the basestation may determine a parameter for RAN paging adjustment based on thecore network parameter for paging. In an example, the core networkparameter for paging and the parameter for RAN paging adjustment may besame. In an example, the base station may modify the core networkparameter for paging to the parameter for RAN paging adjustment based oncongestion situation of the base station, allocated paging resourcesituation, and/or the like.

In an example, the base station may send a context setup responsemessage in response to receiving the context setup request message fromthe AMF. In an example, the context setup response message may be aninitial context setup response. In an example, the context setupresponse message may be a UE context modification response message. Inan example, the context setup response message may AMF UE NGAP ID, RANUE NGAP ID, PDU session resource setup response list, PDU sessionresource failed to setup list and/or the like.

In an example, the base station may detect an inactivity of the UE anddetermine to suspend an RRC connection with the UE. In an example, thebase station may send an RRC release message to the UE in response tothe determination. In an example, the RRC release message may comprisesuspension/suspend configuration information, the parameter for RANpaging adjustment, and/or the like.

In an example, the suspension/suspend configuration information maycomprise a radio network temporary identity (RNTI), a radio accessnetwork (RAN) paging cycle, a RAN notification area (RNA) information, aperiodic RNA update time value, and/or the like. In an example, the RANnotification area information may comprise a list of cells, a PLMNidentity, a list of tracking area codes, a list of RAN area code, and/orthe like.

In an example, the parameter for RAN paging adjustment may comprise apaging time offset comprising number of radio frames and/or number ofradio sub-frames, a paging UE identity offset, frequency/bandinformation for paging, frequency/and information not used for paging,paging repetition number, an indication that a UE specific discontinuousreception (DRX) is prioritized and/or the like.

In an example, a paging frame (PF) based on the paging adjustmentparameter may be incremented with the paging time offset in response tothe paging adjustment parameter being the paging time offset. In anexample, the final PF of FIG. 19C may be system frame number (SFN) 38 inresponse to the initial PF is SFN 30 and the paging time offset is SFN8.

In an example, the paging time offset may be used to replace thePF_offset in the equation of FIG. 19D. In an example, the PF_offset iscell specific paging offset value. In an example, the UE and the basestation may use the paging time offset instead of the cell specificpaging offset ‘PF_offset’.

In an example, the UE_ID in FIG. 19C and FIG. 19D may be incrementedbased on the paging UE identity offset, in response to the pagingadjustment parameter being the paging UE identity offset. In an example,IMSI of the UE is ‘1234123412341234’ and the paging UE identity offsetis ‘1021’ then the UE_ID for calculation of the paging frame and thepaging occasion may be the IMSI (1234123412341234) plus the paging UEidentity offset (1021) and the UE_ID may be ‘12341234123412342255’.

In an example, the UE may monitor frequencies/bands for paging receptionin the frequency/band information for paging, in response to the pagingadjustment parameter being the frequency/band information for paging.

In an example, the UE may not monitor frequencies/bands for pagingreception in the frequency/band information not used for paging, inresponse to the paging adjustment parameter being the frequency/bandinformation not used for paging.

In an example, the UE may monitor consecutive system frame number forpaging, in response to the paging adjustment parameter being the pagingrepetition number. In an example, the calculated paging frame usingquestion 19.C and 19.C is SFN 34 and the paging repetition number is 2,then the UE may monitor the system frame number 34, 35, 36 for pagingreception.

In an example, the UE may use the UE specific discontinuous reception(DRX) value instead of a default DRX value of the base station, inresponse to the paging adjustment parameters being the indication that aUE specific discontinuous reception (DRX) is prioritized. In an example,the T value of the FIG. 19B is Tue. In an example, the UE may not employmin (Tue, Tc) condition in response to the paging adjustment parametersbeing the indication that a UE specific discontinuous reception (DRX) isprioritized. In an example, the UE specific DRX may be the radio accessnetwork (RAN) paging cycle.

In an example, the UE may receive the paging message successfully. In anexample, the UE may send an RRC resume request message to the basestation in response to receiving the paging message. In an example, thebase station may respond by sending an RRC resume message in response toreceiving the RRC resume request message. In an example, the previouslyconfigured RRC connection may be successfully resumed between the UE andthe base station. The base station may transfer a packet data or a NASPDU to the UE.

FIG. 31 illustrates an example embodiment of a radio access networkparameter configuration update procedure between a UE and, a basestation, an AMF and a server. In an example, the server may be a networkdata analytics function (NWDAF). In an example, the server may be anoperations, administration and management (OA&M) function.

In an example, the UE may detect an occurrence of a paging collision(between serving network (e.g. PLMN 1) and other system network). In anexample, the UE may send a paging collision indication message to theAMF. In an example, the UE may send a paging collision indicationmessage to the server via the AMF. In an example, the paging collisionindication message may comprise a PLMN identity, cause value, and/or thelike. In an example, the PLMN identity may the identity of a neighborPLMN which the UE detects a paging collision with the serving PLMN. Inan example, the neighbor PLMN may a PLMN that provide services in a widearea (e.g. country, continental). In an example, the servicing PLMN mayprovide services in a smaller area (e.g. city or state). In an example,the cause value may indicate an occurrence of a paging collision.

In an example, the serving PLMN may not provide voice service to the UEand may want to configure paging parameters/DRX parameters based onneighbor PLMN paging parameters/DRX parameters. In an example, theserving PLMN may want to avoid a paging collision with a neighbor PLMNwhich provide voice service to the UE.

In an example, the serving PLMN (e.g. PLMN 1) may indicate to the UEsreporting any occurrence of paging collision. In an example, servingPLMN may provide a certain PLMN identity which the serving PLMN want toknow the configuration of paging parameters/DRX parameters. In anexample, the server or the AMF of the serving PLMN (e.g. PLMN 1) maysend a paging collision report request message to the UE in response toreceiving the paging collision indication message. In an example, theserving PLMN may request paging collision report based on the PLMNidentity of the paging collision indication message. In an example, theserving PLMN may not ask a paging collision report from the UE if thePLMN identity is not interest for paging collision resolving for theserving PLMN.

In an example, the AMF or the server may send a paging collision reportrequest message to the UE in response to receiving the paging collisionindication message. The paging collision report request message maycomprise a PLMN identity and required parameters.

In an example, the UE may send a paging collision report message to theAMF or the Server. In an example, the UE may send the paging collisionreport message in response to receiving the paging collision reportrequest message. In an example, the paging collision report message maycomprise a PLMN identity of a neighbor PLMN, paging configurationparameters of the PLMN, and/or the like. In an example, the UE maydetermine the paging configuration parameters based on the requiredparameters. The paging configuration parameters (e.g. Tc, nB, PF_Offset,i_s) may comprise DRX parameters which are broadcasted by a base stationof the neighbor PLMN.

In an example, the AMF or the server may receive the paging collisionreport message from multiple UEs which experienced the paging collision.The AMF or the Server may determine new paging parameters/DRX parametersof the serving PLMN based on the paging configuration parameters of theneighbor PLMN and may send to the base stations of the serving PLMN.

FIG. 32, FIG. 33 and FIG. 34 are example flow chart illustrating how aUE determine paging adjustment is required to resolve paging collisionsituation or UE battery efficiency and/or the like.

In FIG. 32, a UE may register a second PLMN. The UE may receive systeminformation from a base station of a first PLMN. The UE may read thesystem information. The UE may detect that paging adjustment is neededdue to paging collision between the first PLMN and the second PLMN. Ifthe UE determines that paging adjustment is needed, the UE may send aregistration request message to an AMF of the first PLMN. Theregistration request message may comprise paging adjustment informationto avoid paging collision with the second PLMN. If the UE determinesthat paging adjustment is not needed, the UE may send a registrationrequest message to the AMF of the first PLMN. The registration requestmessage may not comprise paging adjustment information.

In FIG. 33, a UE may register a second PLMN and a first PLMN. If the UEdetects paging collision between the first PLMN and the second PLMN, theUE may determine which PLMN is primary PLMN. In an example, the primaryPLMN may be a higher priority PLMN for the UE. If the second PLMN is aprimary PLMN, the UE may send a registration request message to an AMFof the first PLMN, requesting a need of paging adjustment and pagingadjustment information. If second PLMN is not a primary PLMN, the UE maysend a registration request message to an AMF of the second PLMN,requesting a need of paging adjustment and paging adjustmentinformation.

In FIG. 34, a UE may register a second PLMN. The UE may receive systeminformation of a base station of a first PLMN. The UE may read thesystem information and my detect whether paging adjustment needed forpower saving of the UE. If the UE determine that paging adjustment forpower saving between the first PLMN and the second PLMN is needed, theUE may derive preferred paging monitoring occasion of the first PLMNwhich is adjacent to the paging occasion of the second PLMN. Based onthe paging adjustment, the UE may wake up one time in a given DRX periodand monitor both paging from first PLMN and the second PLMN. The UE maysend a registration request message to an AMF of the first PLMN. Theregistration message may comprise paging adjustment information toassist energy efficient paging monitoring. If the UE determine thatpaging adjustment for power saving is not needed, the UE may send aregistration request message to the AMF of the first PLMN without thepaging adjustment information.

In an example, a wireless device may send to an access and mobilitymanagement function (AMF), a registration request message requesting aregistration to a serving public land mobile network (PLMN), theregistration request message comprising paging adjustment informationfor normal paging of the wireless device.

In an example, the wireless device may receive from the AMF, aregistration accept message, indicating a successful registration withthe serving PLMN, the registration accept message comprising pagingadjustment parameters for normal paging.

In an example, the wireless device may receive from a base station, aradio resource control (RRC) release message to transition the wirelessdevice from an RRC connected state to an RRC idle state.

In an example, the wireless device may determine, a paging monitoringoccasion, based on the paging adjustment parameters and systeminformation for paging.

In an example, the wireless device may receive, paging messages in thepaging monitoring occasion.

In an example, the wireless device may send to the base station, an RRCmessage to request a connection setup.

In an example, the wireless device may be connected to a public landmobile network (PLMN) that is different from the serving PLMN thatcomprises the AMF.

In an example, a side link communication of the wireless device may beactivated.

In an example, a multimedia broadcast/multicast system communication ofthe wireless device may be activated.

In an example, the paging adjustment information may comprisesnon-preferred system frame number for paging, preferred system framenumber for paging, a conflicted system frame number for paging, arequested paging offset value represented as a system frame number, arequested paging offset value represented as a time period, a requestedpaging offset value represented as a UE identity, an indication thatpaging repetition is required, an indication that paging occasion isconflicted, a requested paging repetition number, non-preferredfrequency/band for paging, preferred frequency/band for paging, anindication that a UE specific discontinuous reception (DRX) beingpreferred, and/or the like.

In an example, the wireless device may determine the paging adjustmentinformation based on a paging monitoring occasion of a public landmobile network (PLMN) A that is different from the serving PLMN thatcomprises the AMF and the base station.

In an example, the determining may be further based on a pagingcollision between a paging monitoring occasion of the serving PLMN andthe paging monitoring occasion of the PLMN A.

In an example, the determining may be further based on how to allocate apaging monitoring occasion of the serving PLMN approximate time to thepaging monitoring occasion of the PLMN A.

In an example, the determining may be further based on adjacent time ofthe paging monitoring occasion of the PLMN A.

In an example, the wireless device may determine the paging adjustmentinformation based on a monitoring time for a side link communication.

In an example, the wireless device may determine the paging adjustmentinformation based on a monitoring time for a multimediabroadcast/multicast system communication.

In an example, the paging adjustment parameters may comprise a pagingtime offset comprising number of radio frames and/or number of radiosub-frames, a paging UE identity offset, frequency/band information forpaging, frequency/band information not used for paging, pagingrepetition number, an indication that a UE specific discontinuousreception (DRX) is prioritized, and/or the like.

In an example, a paging monitoring occasion may be shifted based on thepaging time offset in response to the paging adjustment parameters beingthe paging time offset.

In an example, the UE specific discontinuous reception (DRX) value maybe used instead of a default DRX value of the base station, in responseto the paging adjustment parameters being the indication.

In an example, the UE specific DRX may be provided by the wirelessdevice to the AMF during registration procedure with the serving PLMN.

In an example, system information of the base station may comprise thedefault DRX value.

In an example, a UE identity may be used for an equation of the pagingmonitoring occasion.

In an example, the paging UE identity offset may be used to modify theUE identity for the equation, in response to the paging adjustmentparameters being the paging UE identity offset.

In an example, the paging repetition number may be used toreceive/transmit paging message based on a paging monitoring occasion.

In an example, the frequency/band information for paging may be used forcell selection/reselection of the wireless device as a higher priorityfrequency/band.

In an example, the frequency/band information not used for paging may beused for cell selection/reselection of the wireless device as a lowerpriority frequency/band.

In an example, a wireless device may send to an access and mobilitymanagement function (AMF), a registration request message requesting aregistration to a public land mobile network (PLMN), the registrationrequest message comprising paging adjustment information for normalpaging of the wireless device.

In an example, the wireless device may receive from the AMF, aregistration accept message, indicating a successful registration withthe PLMN, the registration accept message comprising paging adjustmentparameters for normal paging.

In an example, the wireless device may receive from a base station, aradio resource control (RRC) release message to transition the wirelessdevice from an RRC connected state to an RRC inactive state, the RRCrelease message comprising paging adjustment parameters for radio accessnetwork (RAN) paging.

In an example, the wireless device may determine, a paging monitoringoccasion, based on the RAN paging adjustment parameters and systeminformation for RAN paging.

In an example, the wireless device may receive, paging messages in thepaging monitoring occasion.

In an example, the wireless device may send, to the base station, an RRCmessage to request a connection resumption.

In an example, a base station may receive from an access and mobilitymanagement function (AMF), a core network assistance information toassist a radio access network (RAN) paging, the core network assistanceinformation comprising a core network parameter for paging adjustment ofa wireless device.

In an example, the base station may send to the wireless device, a radioresource control (RRC) message to transition the wireless device from anRRC connected state to the RRC inactive state, the RRC messagecomprising a parameter for RAN paging adjustment based on the corenetwork parameter.

In an example, the base station may send to the wireless device, the RANpaging based on the parameter for the RAN paging adjustment.

In an example, the base station may receive from the wireless device, anRRC message to request a connection resuming with the wireless device.

In an example, wherein the wireless device may be connected to a publicland mobile network (PLMN) that is different from a PLMN that comprisesthe AMF and the base station.

In an example, a side link communication of the wireless device may beactivated.

In an example, a multimedia broadcast/multicast system communication ofthe wireless device may be activated.

In an example, the core network parameter comprises non-preferred systemframe number for paging, preferred system frame number for paging, aconflicted system frame number for paging, a requested paging offsetvalue represented as a system frame number, a requested paging offsetvalue represented as a time period, a requested paging offset valuerepresented as a UE identity, an indication that paging repetition isrequired, an indication that paging occasion is conflicted, a requestedpaging repetition number, non-preferred frequency/band for paging,preferred frequency/band for paging, an indication that a UE specificdiscontinuous reception (DRX) being preferred.

In an example, the core network parameter comprises a paging time offsetcomprising number of radio frames and/or number of radio sub-frames, apaging UE identity offset, frequency/band information for paging,frequency/band information not used for paging, paging repetitionnumber, an indication that a UE specific discontinuous reception (DRX)is prioritized, and/or the like.

In an example, the parameter for RAN paging comprises a paging timeoffset comprising number of radio frames and/or number of radiosub-frames, a paging UE identity offset, frequency/band information forpaging, frequency/band information not used for paging, pagingrepetition number, an indication that a UE specific discontinuousreception (DRX) is prioritized, and/or the like.

In an example, a RAN paging monitoring occasion may be shifted based onthe paging time offset in response to the parameter for RAN paging beingthe paging time offset.

In an example, the UE specific discontinuous reception (DRX) value maybe used for a RAN paging monitoring occasion derivation instead of adefault DRX value of the base station, in response to the parameter forRAN paging being the indication.

In an example, the UE specific DRX may be provided by the wirelessdevice to the AMF during registration procedure with the serving PLMN.

In an example, system information of the base station may comprise thedefault DRX value.

In an example, a UE identity may be used for an equation of the pagingmonitoring occasion.

In an example, the paging UE identity offset may be used to modify theUE identity for the equation, in response to the parameter for RANpaging being the paging UE identity offset.

In an example, the paging repetition number may be used toreceive/transmit paging message based on a paging monitoring occasion.

In an example, the frequency/band information for paging may be used forcell reselection of the wireless device as a higher priorityfrequency/band.

In an example, the frequency/band information not used for paging may beused for cell reselection of the wireless device as a lower priorityfrequency/band.

In an example, the core network parameter may be the parameter for theRAN paging adjustment.

In an example, the core network assistance information may furthercomprise a UE identity index value, a UE specific discontinuousreception (DRX), a periodic registration area update time value, amobile initiated connection only (MICO) mode indication, a registrationarea, an expected UE behavior, and/or the like.

In an example, a network data analytics function (NWDAF) may receivefrom a wireless device, a paging collision indication message toindicate an occurrence of a paging collision with other system, thepaging collision indication message comprising a public land mobilenetwork (PLMN) identity and a cause value.

In an example, the NWDAF may send, to the wireless device, a pagingcollision report request message to request a report of the pagingcollision information.

In an example, the NWDAF may receive from the wireless device, a pagingcollision report message, the paging collision report message comprisinga PLMN identity and paging parameters of the PLMN.

In an example, the NWDAF may determine paging parameters update of abase station based on the received a paging collision report requestmessage.

In an example, the NWDAF may send, to the base station, a pagingparameter configuration message comprising new paging parameters.

According to various embodiments, a device such as, for example, awireless device, a device, a base station, and/or the like, may compriseone or more processors and memory. The memory may store instructionsthat, when executed by the one or more processors, cause the device toperform a series of actions. Embodiments of example actions areillustrated in the accompanying figures and specification. Features fromvarious embodiments may be combined to create yet further embodiments.

FIG. 35 is a flow diagram as per an aspect of an example embodiment ofthe present disclosure. At 3510, a base station may receive from anaccess and mobility management function (AMF), core network assistanceinformation to assist radio access network (RAN) paging. The corenetwork assistance information may indicate that first paging occasionsare conflicted with second paging occasions for a wireless device. At3520, based on the core network assistance information, the base stationmay determine a RAN paging adjustment of the first paging occasions. At3530, the base station may send a radio resource control (RRC) messageto the wireless device. The RRC message may transition the wirelessdevice from an RRC connected state to an RRC inactive state. The RRCmessage may comprise a parameter indicating the RAN paging adjustment.At 3540, the base station may send, to the wireless device, a RAN pagingmessage based on the RAN paging adjustment. At 3550, the base stationmay receive from the wireless device, a second RRC message to request aconnection resuming with the wireless device.

According to an embodiment, the wireless device may be connected to asecond public land mobile network (PLMN). The second PLMN may bedifferent from a PLMN that comprises the AMF and the base station.According to an embodiment, the second paging occasions may beassociated with the second PLMN. According to an embodiment, the firstpaging occasions may be associated with the PLMN. According to anembodiment, the second paging occasions may be associated with a sidelink communication of the wireless device. According to an embodiment,the second paging occasions may be associated with a multimediabroadcast system communication of the wireless device. According to anembodiment, the core network assistance information may comprise anon-preferred system frame number for paging. The core networkassistance information may comprise a non-preferred system frame numberfor a paging preferred system frame number for paging. The core networkassistance information may comprise a conflicted system frame number forpaging. The core network assistance information may comprise a requestedpaging offset value represented as a system frame number. The corenetwork assistance information may comprise a requested paging offsetvalue represented as a time period. The core network assistanceinformation may comprise a requested paging offset value represented asa user equipment identity. The core network assistance information maycomprise an indication that paging repetition is required. The corenetwork assistance information may comprise an indication that pagingoccasion is conflicted. The core network assistance information maycomprise a requested paging repetition number. The core networkassistance information may comprise a non-preferred band for paging. Thecore network assistance information may comprise a preferred band forpaging. The core network assistance information may comprise anindication that a user equipment specific discontinuous reception (DRX)is preferred.

According to an embodiment, the core network assistance information maycomprise a paging time offset comprising number of radio frames andnumber of radio sub-frames. The core network assistance information maycomprise a paging user equipment identity offset. The core networkassistance information may comprise band information for paging. Thecore network assistance information may comprise band information notused for paging. The core network assistance information may comprisepaging repetition number. The core network assistance information maycomprise an indication that a user equipment specific discontinuousreception (DRX) is prioritized.

According to an embodiment, the parameter for RAN paging adjustment maycomprise a paging time offset comprising number of radio frames andnumber of radio sub-frames. The parameter for RAN paging adjustment maycomprise a paging user equipment identity offset. The parameter for RANpaging adjustment may comprise band information for paging. Theparameter for RAN paging adjustment may comprise band information notused for paging. The parameter for RAN paging adjustment may comprisepaging repetition number. The parameter for RAN paging adjustment maycomprise an indication that a user equipment specific discontinuousreception (DRX) is prioritized.

According to an embodiment, the core network assistance information mayfurther comprise a user equipment specific discontinuous reception(DRX). The core network assistance information may further comprise aperiodic registration area update time value. The core networkassistance information may further comprise a mobile initiatedconnection only (MICO) mode indication. The core network assistanceinformation may further comprise a registration area. The core networkassistance information may further comprise an expected user equipmentbehavior.

FIG. 36 is a flow diagram as per an aspect of an example embodiment ofthe present disclosure. At 3610, a wireless device may receive from anaccess and mobility management function (AMF) of a first public landmobile land (PLMN), a registration accept message comprising a firstuser equipment (UE) identity of the wireless device. The first UEidentity may determine first paging occasions of the first PLMN. At3620, the wireless device may determine a collision between the firstpaging occasions and second paging occasions of a second PLMN. At 3630,based on the determination of the collision, the wireless device maydetermine a modification of the first UE identity of the wirelessdevice. At 3640, the wireless device may send to the AMF, a registrationrequest message requesting the modification of the first UE identity. At3650, the wireless device may receive from the AMF, a registrationaccept message comprising one or more parameters determining secondpaging occasions of the first PLMN.

According to an embodiment, the first UE identity may be a 5 generationglobally unique temporary identifier (5G-GUTI). According to anembodiment, the first paging occasions may be based on the 5G-GUTI.

According to an embodiment, the registration request message maycomprise the first UE identity. The registration request message maycomprise a UE identity offset associated with the first UE identity.

According to an embodiment, the wireless device may be amulti-subscriber identity module (SIM) UE. According to an embodiment,the wireless device may be a dual-SIM UE.

FIG. 37 is a flow diagram as per an aspect of an example embodiment ofthe present disclosure. At 3710, a network data analytics function(NWDAF) of a first public land mobile network (PLMN) may receive from awireless device, a paging collision report message indicating a pagingcollision with a second PLMN. The paging collision report message maycomprise a PLMN identity of the second PLMN and first paging parametersof the second PLMN. At 3720, the NWDAF may determine second pagingparameters based on the paging collision report message. At 3730, theNWDAF may send to a base station of the first PLMN, a paging parameterconfiguration message comprising the second paging parameters.

According to an embodiment, the NWDAF may receive a paging collisionindication comprising the PLMN identity of the second PLMN and a causevalue. The NWDAF may send to the wireless device, a paging collisionreport request message based on the paging collision indication.

According to an embodiment, first paging occasions of the second PLMNand second paging occasions of the first PLMN may be conflicted.According to an embodiment, the reception of the paging collision reportmessage may be based on the paging collision report request message.

In this specification, a and an and similar phrases are to beinterpreted as at least one and one or more. In this specification, theterm may is to be interpreted as may, for example. In other words, theterm may is indicative that the phrase following the term may is anexample of one of a multitude of suitable possibilities that may, or maynot, be employed to one or more of the various embodiments. If A and Bare sets and every element of A is also an element of B, A is called asubset of B. In this specification, only non-empty sets and subsets areconsidered. For example, possible subsets of B={cell1, cell2} are:{cell1}, {cell2}, and {cell1, cell2}.

In this specification, parameters (Information elements: IEs) maycomprise one or more objects, and each of those objects may comprise oneor more other objects. For example, if parameter (IE) N comprisesparameter (IE) M, and parameter (IE) M comprises parameter (IE) K, andparameter (IE) K comprises parameter (information element) J, then, forexample, N comprises K, and N comprises J. In an example embodiment,when one or more messages comprise a plurality of parameters, it impliesthat a parameter in the plurality of parameters is in at least one ofthe one or more messages but does not have to be in each of the one ormore messages.

Many of the elements described in the disclosed embodiments may beimplemented as modules. A module is defined here as an isolatableelement that performs a defined function and has a defined interface toother elements. The modules described in this disclosure may beimplemented in hardware, software in combination with hardware,firmware, wetware (i.e. hardware with a biological element) or acombination thereof, which may be behaviorally equivalent. For example,modules may be implemented as a software routine written in a computerlanguage configured to be executed by a hardware machine (such as C,C++, Fortran, Java, Basic, Matlab or the like) or a modeling/simulationprogram such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript.Additionally, it may be possible to implement modules using physicalhardware that incorporates discrete or programmable analog, digitaland/or quantum hardware. Examples of programmable hardware may comprise:computers, microcontrollers, microprocessors, application-specificintegrated circuits (ASICs); field programmable gate arrays (FPGAs); andcomplex programmable logic devices (CPLDs). Computers, microcontrollersand microprocessors are programmed using languages such as assembly, C,C++ or the like. FPGAs, ASICs and CPLDs are often programmed usinghardware description languages (HDL) such as VHSIC hardware descriptionlanguage (VHDL) or Verilog that configure connections between internalhardware modules with lesser functionality on a programmable device.Finally, it needs to be emphasized that the above mentioned technologiesare often employed in combination to achieve the result of a functionalmodule.

Example embodiments of the invention may be implemented using variousphysical and/or virtual network elements, software defined networking,virtual network functions.

The disclosure of this patent document incorporates material which issubject to copyright protection. The copyright owner has no objection tothe facsimile reproduction by anyone of the patent document or thepatent disclosure, as it appears in the Patent and Trademark Officepatent file or records, for the limited purposes required by law, butotherwise reserves all copyright rights whatsoever.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example, and notlimitation. It will be apparent to persons skilled in the relevantart(s) that various changes in form and detail can be made thereinwithout departing from the spirit and scope. In fact, after reading theabove description, it will be apparent to one skilled in the relevantart(s) how to implement alternative embodiments. Thus, the presentembodiments should not be limited by any of the above describedexemplary embodiments. In particular, it should be noted that, forexample purposes, the above explanation has focused on the example(s)using 5G AN. However, one skilled in the art will recognize thatembodiments of the invention may also be implemented in a systemcomprising one or more legacy systems or LTE. The disclosed methods andsystems may be implemented in wireless or wireline systems. The featuresof various embodiments presented in this invention may be combined. Oneor many features (method or system) of one embodiment may be implementedin other embodiments. A limited number of example combinations are shownto indicate to one skilled in the art the possibility of features thatmay be combined in various embodiments to create enhanced transmissionand reception systems and methods.

In addition, it should be understood that any figures which highlightthe functionality and advantages, are presented for example purposes.The disclosed architecture is sufficiently flexible and configurable,such that it may be utilized in ways other than that shown. For example,the actions listed in any flowchart may be re-ordered or optionally usedin some embodiments.

Further, the purpose of the Abstract of the Disclosure is to enable theU.S. Patent and Trademark Office and the public generally, andespecially the scientists, engineers and practitioners in the art whoare not familiar with patent or legal terms or phraseology, to determinequickly from a cursory inspection the nature and essence of thetechnical disclosure of the application. The Abstract of the Disclosureis not intended to be limiting as to the scope in any way.

Finally, it is the applicant's intent that only claims that include theexpress language means for or step for be interpreted under 35 U.S.C.112. Claims that do not expressly include the phrase means for or stepfor are not to be interpreted under 35 U.S.C. 112.

1. A method comprising: deriving, by a wireless device: first pagingoccasions of a first public land mobile network (PLMN) based on aninternational mobile subscriber identity (IMSI) of the wireless device;and second paging occasions of a second PLMN; determining, by thewireless device, a collision between the first paging occasions and thesecond paging occasions; based on determining the collision, sending, bythe wireless device to a core network node of the first PLMN, arequested IMSI offset value for offsetting the IMSI of the wirelessdevice; receiving, by the wireless device from the core network node, anaccepted IMSI offset value for offsetting the IMSI of the wirelessdevice; monitoring, by the wireless device, third paging occasions ofthe first PLMN, wherein the third paging occasions are derived based onan alternative IMSI equal to a sum of: the IMSI of the wireless device;and the accepted IMSI offset value.
 2. The method of claim 1, whereinthe core network node is a mobility management function in a corenetwork of the first PLMN.
 3. The method of claim 1, further comprisingdetermining the requested IMSI offset value based on avoiding acollision between the third paging occasions and the second pagingoccasions.
 4. The method of claim 1, wherein the requested IMSI offsetvalue is included in a request for a registration of the wireless devicethat the wireless device sends to the core network node.
 5. The methodof claim 4, wherein the accepted IMSI offset value is included in anacceptance of the registration of the wireless device that the wirelessdevice receives from the core network node.
 6. The method of claim 1,wherein the wireless device prioritizes the second PLMN over the firstPLMN.
 7. The method of claim 1, wherein the wireless device is amultiple universal subscriber identity module (multi-USIM) device. 8.The method of claim 1, wherein the IMSI of the wireless device isrepresented by a plurality of bits, and the plurality of bits of theIMSI is greater than a number of bits of the requested IMSI offsetvalue.
 9. The method of claim 1, wherein the IMSI of the wireless deviceis represented by a plurality of bits, and the plurality of bits of theIMSI is greater than a number of bits of the accepted IMSI offset value.10. The method of claim 1, wherein the IMSI of the wireless device isrepresented by a plurality of bits, and at least one of the plurality ofbits of the IMSI is not sent by the wireless device to the core networknode.
 11. A wireless device, comprising: one or more processors; andmemory storing instructions that, when executed by the one or moreprocessors, cause the wireless device to: derive: first paging occasionsof a first public land mobile network (PLMN) based on an internationalmobile subscriber identity (IMSI) of the wireless device; and secondpaging occasions of a second PLMN; determine a collision between thefirst paging occasions and the second paging occasions; based ondetermining the collision, send, to a core network node of the firstPLMN, a requested IMSI offset value for offsetting the IMSI of thewireless device; receive, from the core network node, an accepted IMSIoffset value for offsetting the IMSI of the wireless device; monitorthird paging occasions of the first PLMN, wherein the third pagingoccasions are derived based on an alternative IMSI equal to a sum of:the IMSI of the wireless device; and the accepted IMSI offset value. 12.The wireless device of claim 11, wherein the core network node is amobility management function in a core network of the first PLMN. 13.The wireless device of claim 11, wherein the instructions cause thewireless device to determine the requested IMSI offset value based onavoiding a collision between the third paging occasions and the secondpaging occasions.
 14. The wireless device of claim 11, wherein therequested IMSI offset value is included in a request for a registrationof the wireless device that the wireless device sends to the corenetwork node.
 15. The wireless device of claim 14, wherein the acceptedIMSI offset value is included in an acceptance of the registration ofthe wireless device that the wireless device receives from the corenetwork node.
 16. The wireless device of claim 11, wherein the wirelessdevice prioritizes the second PLMN over the first PLMN.
 17. The wirelessdevice of claim 11, wherein the wireless device is a multiple universalsubscriber identity module (multi-USIM) device.
 18. The wireless deviceof claim 11, wherein the IMSI of the wireless device is represented by aplurality of bits, and the plurality of bits of the IMSI is greater thanat least one of: a number of bits of the requested IMSI offset value;and a number of bits of the accepted IMSI offset value.
 19. The wirelessdevice of claim 11, wherein the IMSI of the wireless device isrepresented by a plurality of bits, and at least one of the plurality ofbits of the IMSI is not sent by the wireless device to the core networknode.
 20. A system comprising: a wireless device comprising one or moreprocessors; and memory storing instructions that, when executed by theone or more processors, cause the wireless device to: determine acollision between first paging occasions of a first public land mobilenetwork (PLMN) and second paging occasions of a second PLMN; based onthe determination, send, to a core network node of the first PLMN, afirst message comprising a requested offset value for offsetting aninternational mobile subscriber identity (IMSI); receive, from the corenetwork node, a second message comprising an accepted offset value foroffsetting the IMSI; and monitor third paging occasions determined basedon the accepted offset value; and the core network node, wherein thecore network node comprises one or more processors; and memory storinginstructions that, when executed by the one or more processors, causethe core network node to: receive, from the wireless device, the firstmessage; and send, to the wireless device, the second message.